Wagile Project Management isn't going Anywhere

The reality is that the rigid application of either Agile or Waterfall rarely fits the messy reality of complex delivery. 

In fact, most 'Agile' projects are hybrids in disguise. Project and Programme Managers mostly end up using a blend of methodologies because one alone doesn't cut it. 

➡️ Agile gives you speed, iteration and adaptability

➡️ Waterfall gives you structure and predictability

But most complex initiatives need both. 

Your finance team needs predictable timelines, your users need responsive development. Your compliance team needs structure documentation. 

I love Paul Dandurand's description of a "Hybrid Sandwich" Framework as it perfectly describes the reality of the project delivery I've been doing for years.

𝐓𝐡𝐞 𝐇𝐲𝐛𝐫𝐢𝐝 𝐒𝐚𝐧𝐝𝐰𝐢𝐜𝐡

You need regulatory approval upfront (Waterfall planning) but your build phase demands rapid iteration and customer feedback (Agile execution), followed by structured deployment and compliance sign-off (back to Waterfall).

So the hybrid sandwich looks like this:

🥪 Your "top slice of bread" is Waterfall:  Start up the project

🥗 Your "sandwich filler" is Agile: Design and build

🥪 Your "bottom slide of bread" is Waterfall: Finish the project

𝐇𝐨𝐰 𝐭𝐨 𝐮𝐬𝐞 𝐢𝐭 𝐢𝐧 𝐭𝐡𝐞 𝐬𝐚𝐦𝐞 𝐩𝐫𝐨𝐣𝐞𝐜𝐭

Waterfall phases for:

👉 Initial discovery and requirements gathering

👉 Regulatory approvals and compliance

👉 Infratstructure setup and final deployment

👉 Stakeholder sign-off's and governance gates

Agile phases for:

👉 Product development and feature builds

👉 User testing and feedback incorporation

👉 Rapid prototyping and iteration

👉 Cross-functional team collaboration

What's your experience with hybrid approaches? Are you seeing "hybrid sandwiches" in your organisation?

Read the full article here: https://lnkd.in/ex2anKbA