September 18, 2023
Table of Contents
I am not SAFe-certified. However, as an Agile enthusiast who has scaled engineering teams and delivered complex products, I have studied SAFe extensively and found it to be the most comprehensive framework for understanding how to scale effectively.
Why Scaling Agile Is Hard
Agile methodologies work brilliantly for small teams. But as organizations grow - multiple teams, multiple departments, enterprise-level complexity - the limitations become apparent. How do you coordinate 10 teams working on the same product? How do you align portfolio strategy with team-level sprints?

Several frameworks address this: Scrum@Scale (S@S), LeSS (Large-Scale Scrum), Nexus, and Disciplined Agile Delivery. Among these, the Scaled Agile Framework (SAFe) stands out as the most versatile and widely adopted.
What Is SAFe?

Introduced in 2011, SAFe is a comprehensive knowledge base combining Lean, Agile, and DevOps methodologies. It is designed to scale Agile practices, not replace them. The framework is configurable - supporting everything from a few teams to hundreds of people delivering complex systems.
Why SAFe Over Alternatives?

16th Annual State of Agile Report, Dec 2022
| Criteria | SAFe | Other Frameworks |
|---|---|---|
| Comprehensiveness | Full guidance from team to portfolio level | Often focused on one level |
| Flexibility | 4 configurations for different org sizes | Typically one-size-fits-all |
| Adoption | Most widely adopted scaling framework | Smaller communities |
| Training & Support | Extensive certification ecosystem | Limited resources |
| Evolution | Actively maintained (v6.0 in 2023) | Varies |
The Seven Core Competencies
SAFe v6.0 centres on Business Agility with a customer-centric focus. Seven competencies form the foundation:

- Team and Technical Agility - High-performing, cross-functional teams with strong engineering practices
- Agile Product Delivery - Lean-Agile principles for prioritizing, planning, and validating based on customer feedback
- Enterprise Solution Delivery - Coordinating multiple Agile Release Trains (ARTs) for large, complex solutions
- Lean Portfolio Management - Aligning strategy with execution to optimize value flow
- Organizational Agility - Building a culture of continuous learning that embraces change
- Continuous Learning Culture - Knowledge sharing, experimentation, and learning from failures at all levels
- Lean-Agile Leadership - Leaders who foster a Lean-Agile mindset and lead by example with empowerment and trust
From my experience, competency #7 (Lean-Agile Leadership) is the most critical and the most frequently underestimated. Without leaders who genuinely embody these principles, the framework becomes ceremony without substance.
SAFe Configurations
SAFe provides four configurations built from four levels: Team, ART (Agile Release Train), Solution, and Portfolio.

| Configuration | Levels Included | Best For |
|---|---|---|
| Essential SAFe | Team + ART | Small-to-medium organizations starting with SAFe |
| Large Solution SAFe | Team + ART + Solution | Organizations building complex, multi-ART solutions |
| Portfolio SAFe | Team + ART + Portfolio | Organizations needing strategic alignment across multiple products |
| Full SAFe | Team + ART + Solution + Portfolio | Large enterprises with complex solutions and portfolio governance |
Team and ART are mandatory in all configurations - they form the execution backbone.
The Four Core Values

- Alignment - Everyone working toward a common purpose. Minimizes waste, reduces conflicts, enables strategic execution.
- Transparency - Open information sharing enables effective decisions and builds trust. No hidden agendas.
- Respect for People - Individuals are the most important asset. Psychological safety, diverse perspectives, and mutual trust are non-negotiable.
- Relentless Improvement - Continuous experimentation, learning, and adaptation. Retrospectives are not optional.
These values resonate strongly with my own leadership philosophy. Alignment without transparency breeds distrust. Transparency without respect for people becomes surveillance. All four must work together.
My Honest Take

SAFe is comprehensive - arguably too comprehensive for some organizations. The risk is adopting the full framework when Essential SAFe would suffice, creating overhead that defeats the purpose of Agile.
My advice: start with Essential SAFe. Get the Team and ART levels working well. Only add Solution or Portfolio layers when the organizational complexity genuinely demands it. And always remember that the framework is a guide, not a rulebook. Adapt it to your context, measure what matters, and iterate relentlessly.
Share :
You May Also Like

Tech Debt: From a Technical Jargon to Real-World Impacts
What Started This I recently gave a presentation at my company about tech debt - sharing knowledge, techniques, and experiences on how to manage it properly and efficiently. The response convinced me …
Read More
The Modern Leader
The False Dichotomy A bad manager sacrifices people for numbers. A good manager sacrifices numbers for people.
Read More