Beyond the innovator’s dilemma
summary
Shows how a series of companies escape the innovator’s dilemma by doing continuous renovation: replace a 30 million line legacy stack (18M COBOL, 12M Java) in 4.5 years with ~350k lines of microservices, enforce 80% Sonar coverage, run pipelines that take 5–7 minutes, drop pull requests for pair/ensemble programming, organize into autonomous microteams (13–40 people) and allocate a 70/20/10 time split for innovation/renovation/bugs to enable continuous delivery and shorter feedback cycles.
AI-written summary · about
chapters (15)
- 0:00Changing software challenges
- 3:55Quality vs time and cost
- 6:04Technical debt consequences
- 11:43Technical death examples
- 14:31Innovator’s dilemma explained
- 17:21Continuous renovation for legacy
- 22:18Why projects fail
- 26:08Time for innovation
- 30:25Beyond Scrum to delivery
- 35:01Automate for feedback
- 43:13Team ownership unit
- 47:43Empower teams with trust
- 51:15Micro-team collaboration
- 55:30Adapting strategies
- 59:19Keep learning and fun
related talks
01h 03mBeyond the innovator’s dilemma
01h 02mSurviving the Innovators Dilemma
55mGetting Unstuck Strategies for Surviving in a Rapidly Changing Post-Agile World
54mGetting Unstuck. Strategies for Surviving in a Rapidly Changing Post-Agile World
01h 02mGetting Unstuck. Strategies for Surviving in a Rapidly Changing Post-Agile World
43mHow to Innovate in a Legacy
47mGo Faster: Remove the Inhibitors to Innovation
42mSabotaging a Transformation