SAFe (Scaled Agile Framework)
Scaled Agile Framework (SAFe) is a set of organisation and workflow patterns intended to guide enterprise-wide Agile practices across multiple teams.
Core Concepts
- Four Configurations: Essential SAFe, Large Solution SAFe, Portfolio SAFe, and Full SAFe.
- Agile Release Train (ART): A long-lived team of Agile teams that incrementally delivers value in a Program Increment (PI).
- Program Increment (PI) Planning: A multi-team cadence event for synchronising alignment, dependencies, and delivery objectives.
- Lean-Agile Principles: Combines Agile delivery, Lean systems thinking, and DevOps practices.
- Key Roles: Includes Product Owners, Scrum Masters, Release Train Engineers (RTEs), Solution/System Architects, and Enterprise Architects.
Scrum of Scrums (SoS)
The Scrum of Scrums (SoS) is a scaled synchronisation event in SAFe (and broader Agile scaling frameworks) designed to align multiple cross-functional teams working on the same Agile Release Train (ART) or initiative.
Definition & Purpose
While a standard Daily Scrum coordinates individuals within a single team, the Scrum of Scrums coordinates dependencies, risks, and progress between teams. It typically meets 2–3 times a week (or daily during critical release windows) and is facilitated by the Release Train Engineer (RTE) or a lead Scrum Master.
Key Focus Areas
- Dependency Tracking: Resolving cross-team blockers and technical handoffs before they delay delivery.
- Impediment Escalation: Identifying systemic issues that individual Scrum teams cannot resolve on their own and escalating them to leadership or system architects.
- Progress Alignment: Ensuring all teams remain aligned with overall Program Increment (PI) objectives.
- Risk Mitigation: Identifying emerging architectural, integration, or resource risks across team boundaries.
Strategic Utility for CTOs
- Cross-Team Alignment: Provides structured visibility into inter-team dependencies without micromanaging individual squad daily standups.
- Early Warning System: The Scrum of Scrums acts as an early indicator for architectural drift, integration bottlenecks, or delivery delays across the release train.
- Pragmatic Scaling: Allows technology leaders to scale engineering velocity across dozens of teams while maintaining clear accountability and aligned delivery cadences.
Explore Next
- Scrum — Core Agile framework for small cross-functional teams.
References
- Scaled Agile Framework (SAFe)Wikipedia — Overview of SAFe methodology and enterprise Agile practices.