Getting Unstuck. Strategies for Surviving in a Rapidly Changing Post-Agile World
summary
Companies escape technical death by doing continuous renovation: create a tech board that vets ideas against a clear three‑year dot on the horizon, vote weekly and allocate 20% time for small bets, and break work into deployable features handled by rotating microteams of 2–4 people. Automate everything with a CI/CD pipeline and infrastructure as code so changes hit production in minutes (examples cited: 15–18 minute deploys, 20–30 deploys/day). Case studies include an 18M‑line COBOL mainframe and an e‑commerce app stuck for 2.5 years.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 3:15Tech org problems and getting unstuck
- 7:50Technical depth and its impact
- 11:26E-commerce technical decline case study
- 17:44Introduction
- 18:46Continuous renovation concept
- 20:56Cynefin framework and innovation
- 26:10Breaking projects into small features
- 30:20Shortening development cycles
- 37:40Automating for quality and speed
- 39:26Teams and autonomy in development
- 44:16Removing rules and embracing simplicity
- 48:47Continuous renovation and innovation
- 50:30Q&A on small features and culture
- 58:34Q&A on autonomy and rules
- 59:38Closing remarks
related talks
55mGetting Unstuck Strategies for Surviving in a Rapidly Changing Post-Agile World
41mSabotaging an Agile Transformation
01h 02mSurviving the Innovators Dilemma
01h 03mBeyond the innovator’s dilemma
51mSabotaging a Transformation
01h 00mBeyond the innovator’s dilemma
01h 22mAgile - The Road Towards Organizational Agility - Progress & Challenges Examined
47mAgile experience in changing environments and the challenges faced