Facilitating “Quick Waterfall” to Value-Driven Agile
summary
Argues that shifting a big waterfall program to agile fails unless value is managed end to end, with concrete steps: baseline then track through the quarter, value leakage ~50% and start small and measure adoption. Uses iterative value cycles overlaid on delivery, ties team metrics (time to market, bugs) to business KPIs (new users, P&L, cost), shows one client moving from one team to 80% digital coverage and cutting costs while improving outcomes. Practical tools: baseline metrics, adoption KPIs, and governance to enforce ownership.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:59Why large transformations fail
- 5:31Waterfall to agile without losing value
- 8:20Quick Waterfall for value tracking
- 11:32Value mindset in agile cycles
- 14:24Legacy modernization example
- 17:41Scaled agile value measurement
- 23:03Agile transformation case study
- 26:35Agile reorganization reflections
- 29:51Key takeaways
- 30:11Q&A