Get agile and don't die trying
summary
Two years of moving an eight‑person internal team from ad hoc delivery to disciplined agile produces concrete rules: start with weekly one‑hour retrospectives, prefer a switch from Kanban to Scrum when flow discipline fails, pilot on start with new projects for three months, expect some attrition (roughly a third quoted in literature, fewer in practice), change hiring to match new roles, use coaches rather than one‑off training, and treat tools as a package — it helps, but the transformation is unfinished.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:07Agile isn't magic
- 3:34Agile needs effort
- 6:04Clear objectives and team
- 7:27Start small scale
- 9:13External help and coaching
- 11:20Define processes first
- 12:43Respect time focus
- 14:07Team adaptation issues
- 15:34Recruitment and culture
- 18:04Scrum vs Kanban
- 19:50New projects first
- 21:14Use full frameworks
- 22:38Weekly retrospectives
- 23:22Rewarding but hard
related talks
38mPolyglot Agile
51mDon't Kill Agility with Agile Processes
26mAgile Transformations are not about software
36mOne Agile Transformation and two beers please
24m5 Lessons Learned During Agile Transformations
04mAgile Transition - How to Build an Effective Agile Team
22mThe Courage to Continue and Cultural Intelligence — Insights from Agile Practice i...
43mWhy Agile transformation fail