Are you embarking on a new project, filled with ambition and a vision for impactful changes? Amidst this excitement lies a pivotal decision: which project delivery method to choose? While the choice between agile, waterfall, or hybrid methods may seem straightforward, the reality is far more nuanced. Making this decision involves navigating and considering the myriad of factors at play – from project scope and timeline to organisational culture and stakeholder buy-in. Recent research by Thesing et al. [1] provides valuable insights into this dilemma, drawn from desk research and expert interviews.

About the Methods 🔍

1. Classic/Waterfall: This method follows a linear and sequential approach, characterised by extensive upfront planning and a focus on delivering the entire project scope at once. While offering stability, predictability, and detailed planning, it can be rigid and less responsive to changes.
2. Agile: Agile methods, such as Scrum and Kanban, emphasise iterative development, frequent customer collaboration and feedback, and flexibility to adapt to changing requirements. They are particularly beneficial for projects with dynamic and uncertain requirements but may require a cultural shift.
3. Hybrid: Hybrid approaches integrate elements of both classic and agile methods, allowing for flexibility while retaining the structure and predictability of the classic approach. They combine the strengths of both methods but require careful integration and may increase complexity.

Key Challenges in Method Decision

⚙️ Balancing the need for stability with the desire for flexibility.

⚙️ Aligning project management methodologies with organisational culture and project requirements.

⚙️ Ensuring stakeholder buy-in and support for the chosen method.

Introduction of a Decision Model 🎬

To aid in this decision-making process, a two-step Decision Model has been developed by Thesing et al. [1]. The first step involves exclusion criteria, which eliminate Agile as the primary method based on project and organisational characteristics. The second step involves 15 selection criteria covering scope, time, costs, organisational context, and project team characteristics, helping to determine the suitability of Waterfall or Agile. Each criterion is scored between 4 and 0, with 4 indicating full applicability and 0 indicating non-applicability. A high score suggests a good fit for a classical waterfall approach, while a low score indicates that agile methods are better suited. If considering a hybrid approach, Reiff & Schlegel’s systematic literature review [2] sheds light on various hybrid methodologies like Water-Scrum-Fall, Waterfall-Agile, Hybrid V-model, and Agile-Stage-Gate.

Benefits of the Decision Model

🌟 Provides a systematic and comprehensive approach to selecting the most suitable project delivery method.

🌟 Incorporates input from project managers, organisational leaders, and other stakeholders.

🌟 Enhances project success by aligning the chosen method with project characteristics and organisational context.

Three Key Takeaways

📝 Understand the unique characteristics and requirements of your project before selecting a delivery method.

📝 Consider both the advantages and disadvantages of each approach to make an informed decision.

📝 Utilise decision-making tools, such as the two-step model, to guide your selection process and increase the likelihood of project success.

Call for Action 📣

Need help choosing between agile, waterfall, or hybrid project delivery methods? Take the first step towards informed decision-making by exploring these models or consulting with project management experts.

References

1. Thesing, T., Feldmann, C., & Burchardt, M. (2021). Agile versus waterfall project management: decision model for selecting the appropriate approach to a project. Procedia Computer Science, 181, 746–756.
2. Reiff, J., & Schlegel, D. (2022). Hybrid project management – a systematic literature review. International Journal of Information Systems and Project Management, 10(2), 45–63.

‍