Getting Unstuck Strategies for Surviving in a Rapidly Changing Post-Agile World
summary
Companies reach technical death with examples like 188M lines COBOL plus 12M Java, unable to deploy for years; the remedy offered is concrete: allocate 70/20/10 time for horizon features/renovation/bugs, stop projects and ship tiny features, build a multilingual comment system as a concrete outcome, automate tests and CI/CD so a 14-minute pipeline can push to production, form collectives and microteams with real autonomy, run experiments that are allowed to fail, and shrink cycles and components to regain speed.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 1:04Understanding quality
- 5:40Organizations stuck technically
- 7:24Technical debt examples
- 12:15Root causes of stagnation
- 13:18Innovator's dilemma impact
- 16:27Getting unstuck strategies
- 17:53Cynefin framework
- 21:21Experimentation key to innovation
- 24:30Small steps for meaningful change
- 26:14Clear organizational horizon
- 28:40Prioritizing work balance
- 30:46Software dev cycles evolution
- 32:11Rethinking agile frameworks
- 35:40Value via rapid feedback
- 37:23Automating for faster delivery
- 39:51Quality in product pipeline
- 42:22Teams in complex development
- 45:08Autonomy and problem-solving
- 47:11Simplifying rules for teams
- 48:37Practical team autonomy
- 51:46Scaling the approach
- 52:48Summary
related talks
01h 02mGetting Unstuck. Strategies for Surviving in a Rapidly Changing Post-Agile World
01h 03mBeyond the innovator’s dilemma
01h 02mSurviving the Innovators Dilemma
41mSabotaging an Agile Transformation
01h 00mBeyond the innovator’s dilemma
51mSabotaging a Transformation
01h 22mAgile - The Road Towards Organizational Agility - Progress & Challenges Examined
01h 01mFrom 'Agile Hangover' to 'Antifragile Organisations'