Beyond the innovator’s dilemma
summary
Companies hit by legacy code and competing entrants have to choose concrete moves: replace 18 million lines of COBOL and 12 million of Java or accept slow death, or break monoliths that fed a two‑million‑device VPN. Teams build full CI/CD pipelines (lint, unit tests, Sonar, API and end‑to‑end tests), deploy via infrastructure‑as‑code and release continuous delivery at ~20–40 deploys per day. Governance uses a tech board and a 70/20/10 time split; work moves to small, autonomous microteams that remove sprints and retrospectives and run experiments. Some transitions succeed, some fail.
AI-written summary · about
chapters (12)
- 0:00Introduction and title change
- 1:19Why organizations get stuck
- 7:39Technical debt and death examples
- 12:12Innovator’s dilemma explained
- 15:25Speaker introduction
- 17:29Getting unstuck with continuous renovation
- 22:50Complexity zones and experiments
- 24:59Delivering smaller features faster
- 32:01Evolving beyond Scrum
- 41:30Automating releases and pipelines
- 47:02Team autonomy and micro-teams
- 59:46Retrospective and conclusion
related talks
01h 02mSurviving the Innovators Dilemma
01h 00mBeyond the innovator’s dilemma
55mGetting Unstuck Strategies for Surviving in a Rapidly Changing Post-Agile World
01h 02mGetting Unstuck. Strategies for Surviving in a Rapidly Changing Post-Agile World
25mTransforming legacy software
46mWhen Software Becomes Everyone's Job
59mThe continuous culture
58mKeynote: Seven Habits of a (Mostly) Successful Team