Surviving the Innovators Dilemma
summary
Companies actually replace mainframes and 18 million lines of COBOL by breaking work into small deployable pieces, shipping feature-by-feature to a live site that sells 1,500 deals a day. The team automates CI/CD so a service builds, tests and deploys in 5–7 minute pipeline cycles across about 150 codebases, enabling continuous delivery and rotating micro teams that form, deliver, and disband; some migrations succeed, some hit standstill, some require organizational change to work.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:08Software quality vs cost
- 8:54Technical debt impact
- 17:21Innovator's dilemma explained
- 20:53Breaking complexity
- 25:31Navigating Cynefin
- 31:49Development cycles evolution
- 35:18Prerequisites for continuous delivery
- 40:32Autonomy in teams
- 53:48Summary
- 54:29Q&A
related talks
01h 03mBeyond the innovator’s 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
39mImplementing Programmer Anarchy
47mGo Faster: Remove the Inhibitors to Innovation
55mContinuously Delivering Continuous Delivery
17mBeyond DevOps – Holistic transformations in uncertain times