Is SAFe Evil?
summary
SAFe is applied at Lego as a practical toolbox: every eight weeks a two‑day PI planning event gathers ~140 people from 21 teams to build team boards, a giant program board mapping sprint lanes and dependencies, and a shared backlog of features. A Release Train Engineer role coordinates work, an Agile Release Train of teams self‑organizes, and the last IP Sprint is kept as buffer. Results: greater transparency and predictability, more cross‑team pulling of people, but more meetings and WIP still needs active reduction.
AI-written summary · about
chapters (30)
- 0:00Introduction
- 10:46Lightning Talks
- 12:06How should this evolve
- 13:42Product Backlog
- 14:36Team Board
- 15:39Program Board
- 17:26Report
- 18:02Plan Review
- 19:22Risk Management
- 20:21Second Day
- 20:56Conclusion
- 21:06Scrum Masters
- 21:31Is SAFe Evil
- 22:02Shoe Hurry
- 24:30Why SAFe
- 25:04Simplicity
- 25:16Inspiration
- 25:30Tools Metaphor
- 25:45Recipes Metaphor
- 26:02Portfolio Process
- 27:37Transparency
- 28:26Impact
- 30:53Momentum
- 32:39Stakeholders
- 33:02Waterfall
- 33:47What we like
- 35:30What we dont like
- 36:50Mount Stupid
- 38:54Wrap Up
- 40:50SAFe for Scrum
related talks
53mOur SAFe journey to follow the sun
46mBetter SAFe Than Sorry
41mThree years with SAFe: this is what stands out
41mThe Realities of Lean-Agile Transformation – FR
04mLightning talk: Stay SAFe with Scrum
58mAgile Panel
58mScaling Agile in Organizations
53mScrum and SAFe Put into Practice: Landing Roles in Reality