Why Safe isn’t safe!!
summary
Examines problems observed with the SAFe (Scaled Agile Framework) implementation: how rituals and fixed quarterly commitments can dehumanize teams, lead to harsh personnel decisions, and produce disconnected, rigid planning. Argues that heavy upstream phases (validation, strategic alignment, business scoping) bloat ideation, prioritize planning over testing and learning, and calls for re-evaluating whether organizations are growing processes or people.
AI-written summary · about
chapters (15)
- 0:00Introduction to Safe
- 2:09User experience with Safe
- 5:37Team management and dependencies
- 8:04Safe principles analysis
- 11:17Systemic thinking in Safe
- 14:04Standardization and innovation
- 16:30Learning cycles and integration
- 18:58Metrics and evaluation in Safe
- 21:26Cadence and inter-team sync
- 23:11Motivation and decision-making
- 24:13Centralized vs decentralized decisions
- 26:19Value-driven organization
- 27:45Critique of roles and hierarchy
- 29:52What to keep from Safe
- 30:56Conclusion and recommendations
