Getting Unstuck. Strategies for Surviving in a Rapidly Changing Post-Agile World
summary
Describes moving organizations from “technical death” (18M lines of COBOL plus 12M Java in one client) to a continuous renovation model using a visible tech board and 70/20/10 time split. Teams build small services, use trunk‑based development, automated tests and a CI/CD pipeline that pushes changes to production in ~30 minutes and aims for hundreds of daily deploys (team reports 50–80/day). Real deliverables: a new command system, returns API and upload stock files; approach reduces release friction and restores innovation.
AI-written summary · about
chapters (10)
- 0:00Introduction and context
- 1:31Quality in software development
- 5:44Technical debt and getting stuck
- 13:06About the speaker and his approach
- 14:28Continuous renovation strategy
- 21:52Stop doing projects, deliver features
- 29:56Short cycles and rapid feedback
- 37:03Automate everything for quality
- 43:25Team autonomy and simplification
- 51:51Conclusion and final advice
related talks
52mSmall Steps Are the Fastest Way Forward: Life Beyond Agile & Scrum
01h 00mBeyond the innovator’s dilemma
01h 22mAgile - The Road Towards Organizational Agility - Progress & Challenges Examined
45mYou can't be agile when you're fighting your code
44mScaling Agile With a Super-Effective Global Delivery Machine
30mHow DevOps is Enabling Lean Application Development
30mTransforming to a Culture of Continuous Improvement
33mReduce Small-Team Culture Shock with Agile