Agility in Large Transformation Programs – An oxymoron?
summary
Examines concrete fixes for huge ERP and cloud moves that routinely miss targets — industry studies show 25–40% of programs exceed budget and only about 2.5% finish on time, one case has 200+ people and 300+ upstream/downstream systems and a 50% schedule overrun. Recommends specific practices: RAID dashboards in Jira, daily team RAID reviews and twice-weekly cross-team dependency huddles, dependency maps, strict decision governance, vertical slicing into MVPs, defined working models, active change management and revisiting vendor contracts.
AI-written summary · about
chapters (8)
- 0:00Agility in large programs
- 7:31Agility oxymoron in transformations?
- 13:59Barriers to agility
- 19:32Managing dependencies
- 28:25Overcoming decision delays
- 31:56Addressing scope creep
- 38:09Improving team dynamics
- 43:50Key takeaways
related talks
43mWhy Agile transformation fail
44mDragging out and failing Agile Transformation – reasons
51mSabotaging a Transformation
41mSabotaging an Agile Transformation
55mGetting Unstuck Strategies for Surviving in a Rapidly Changing Post-Agile World
43mTaking Agile to the Enterprise – strategy lessons from seven years in transformation
23mIts transformation! But, is it though?
45mAgile Transformation Or Just Another Restructure?