Safe havens and trojan horses
summary
Argues that SAFe often looks terrible because organizations misapply it, not because the framework forbids engineering practices, and recommends using SAFe as a Trojan horse to inject good agile—bring in XP engineering, CI/CD and Kanban, slim PI ceremonies, and push outcomes not theater. Gives concrete moves: drop sprint containers to release when ready, use PI planning (often ~150 people) selectively, lean on OKRs, flow metrics and Team Topologies, and contrasts a yearlong IC‑Agile enterprise coach program with lower‑barrier SPC courses.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 7:25SAFe skepticism explained
- 14:10SAFe myths and criticism
- 21:36SAFe as Trojan Horse
- 27:56Agile inside SAFe
- 37:02Key takeaways
- 46:04Q&A
related talks
45mAgile Security Testing - Lessons Learned
29mPainless Agile Security
27mSecurity Learns to Sprint: DevSecOps
01h 04mShifting Security Everywhere
38mChampioning Security for your Agile Development
33mThe Agile Way to Add Sec, Dev & Ops into Waterfall
46mApplication Security in an Agile World
35mWhy Security Initiatives Are Doomed to Fail & What You Can Do About It