Hybrid agile in software engineering : a systematic literature review

Abstract

Context: Waterfall was the preferred methodology for Software Development due to its clearly defined phases, including requirements gathering, design, implementation, testing, deployment, and maintenance. Waterfall suffered from poor time to market and flexibility to adapt to business changes despite its popularity due to completion of phases in a sequential manner. This led to emergence of Agile methodologies in 1990s. Agile became more popular since early 2000 post release of Agile Manifesto in 2001. Also, business needs were changing, customer were no longer ready to wait longer for a product to be released. Companies with legacy systems or processes may find it difficult to fully transition to Agile methodology. This would have prompted them to take a Hybrid Agile which is combining Agile and Waterfall. Moreover, certain industries are bound by regulatory limitations, thus advocating for the combination of Waterfall and Agile methodologies, particularly in scenarios characterized by rigid project timelines and scope, rather than opting for a complete transition to Agile practices.

Objective: The objective of this study was to investigate the perspective of practitioners on Hybrid Agile methodologies. There are diverse methodologies from both Traditional and Agile methodologies that can be integrated to form Hybrid Agile methodology. The objective of this thesis was to understand the current usage of Hybrid Agile in practice, identify the phases of Agile and Waterfall that are commonly combined in hybrid approaches, and provide recommendations for organizations considering adoption of Hybrid Agile methodologies.

Method: A systematic literature review was conducted to identify 18 primary studies. Then the results of those studies were synthesized to answer defined research questions.

Results: The findings provide valuable understanding on current state of Hybrid Agile methodology. This includes practitioner perspective on perceived benefits of combining Agile and Waterfall elements, challenges encountered in implementation, and practical considerations for successful adoption. The research sheds light on various drivers for Hybrid Agile adoption and analysis on effectiveness of Hybrid Agile in meeting project goals. This thesis study highlights the extent to which Hybrid Agile is researched and documented. The research explores specific phases of Agile and Waterfall that are commonly integrated in Hybrid Agile. Additionally, research offered recommendations for organizations considering the adoption of Hybrid Agile methodologies.

Conclusion: This Systematic Literature Review explores into software development practices, examining practitioners' perspectives and the implementation of Hybrid Agile methodologies. It identifies factors influencing adoption, benefits, implementation configurations, challenges, and recommendations. Hybrid Agile is valued for its versatility, combining Agile and Waterfall strengths to address diverse project needs. Despite challenges, organizations increasingly adopt it for its benefits. Recommendations offer strategies to optimize Hybrid Agile methodologies. However, the scarcity of articles on Hybrid Agile highlights the need for further research in this area.