SAFe / LeSS / Spotify · Methodologies & SDLC Deep Dive

Side-By-Side

The Major Frameworks

Framework	Stance	Notable
SAFe (Scaled Agile Framework)	Heavyweight; layers of roles & ceremonies up to portfolio level	PI Planning (10–12 week increments, big room or virtual). Popular in large enterprise.
LeSS (Large-Scale Scrum)	Minimal additions to Scrum; one product backlog, one PO	"Scrum, with as much as possible kept the same." Up to 8 teams; LeSS Huge for more.
Nexus	Scrum + a "Nexus Integration Team" for cross-team dependencies	From Scrum.org; 3–9 teams.
Scrum@Scale	Scrum-of-Scrums with an Executive Action Team	From Jeff Sutherland (Scrum co-creator).
Spotify Model	Squads, Tribes, Chapters, Guilds — organizational pattern, not a process	Famously "even Spotify doesn't use the Spotify model." Useful as a vocabulary.

SAFe at a Glance

Agile Release Train (ART) — 50–125 people aligned to one cadence.
PI Planning — every 10–12 weeks, all teams in the train plan together for two days.
Roles — Release Train Engineer, Product Manager, System Architect, Business Owners.
Levels — Team, Program (Essential SAFe), Large Solution, Portfolio.
Critique — too prescriptive, too much process for process's sake; the original Agile signatories largely don't endorse it.

Tradeoffs

Scaling adds coordination cost. Sometimes the answer is fewer teams, not a bigger framework.
"Two-pizza team" rule of thumb — if a team needs more than two pizzas to feed, it should split.
Conway's Law wins. Your architecture will look like your org chart; design accordingly.
Framework purity matters less than clear shared cadences and minimal handoff friction.
Spotify model isn't a recipe — it's a snapshot of one company at one point. Don't copy it; understand what it solved.
Big upfront training spend for SAFe certifications — Scaled Agile Inc. is a thriving business in its own right.

Continue