What are the main benefits of using an Agile-Waterfall Hybrid model for complex projects?

All answers to this question.

Communication is the only tool that matters here. The hardware guys and software guys need to be in the same room once a week.

   Answered 2024-06-11 by Jennifer White

• Well said! Jennifer is right; silos are the death of hybrid projects. If they aren't talking, they aren't building the same product.

     Commented 2024-06-12 by Michael Thompson

How do you manage the reporting for executives when half the project uses Gantt charts and the other half uses Velocity?

   Answered 2024-06-16 by David Clark

• David, that's the hardest part. I usually create a "Master Gantt" that shows the Waterfall phases as bars and the Agile Sprints as milestones within those bars. It gives the board the high-level timeline they crave while allowing the dev team to keep their flexibility. It's about translating Agile "story points" into "percentage complete" for the executive summary reports.

     Commented 2024-06-17 by Christopher Evans

We used a Hybrid approach for a medical device launch in 2024. We kept the hardware on a Waterfall path because of the long lead times for parts, but ran the software in two-week Sprints. The "Gotcha" is the synchronization points. You must have "Milestone Sprints" where the software is tested against the current hardware prototype. If you wait until the very end, you'll find that the software assumes the hardware does things it physically can't. In our case, having a Business Analyst bridge the gap between the two teams was the only thing that kept the project on its 18-month schedule.

   Answered 2024-11-12 by Barbara Taylor