Framework Value Stream Comparison¶
Context¶
This page compares how major Agile scaling frameworks map to the same underlying value stream.
It is useful when selecting, tailoring, or explaining framework choices without losing sight of the delivery system itself.
See:
Related diagrams:
Related artifacts:
This document compares how major scaling frameworks map to a common value stream:
Idea -> Validation -> Prioritization -> Development -> Integration -> Deployment -> Feedback -> Outcome
1. Structural Mapping Matrix¶
| Value Stream Stage | SAFe | LeSS | Nexus | Scrum at Scale | Disciplined Agile |
|---|---|---|---|---|---|
| Idea intake | Portfolio Epic funnel | Product Backlog | Product Backlog | Executive MetaScrum | Inception |
| Problem validation | Lean Business Case | PO discovery | PO discovery | Product Owner Cycle | Exploration |
| Outcome definition | Portfolio Kanban approval | Refined PBI | Refined PBI | Ordered Product Backlog | Stakeholder vision |
| Backlog refinement | Program Backlog refinement | Multi-team refinement | Cross-team refinement | Team refinement | Continuous backlog evolution |
| Prioritization | PI Planning | Single backlog ordering | Single backlog ordering | MetaScrum alignment | Value-based decision framework |
| Ready for development | PI commitment | Sprint commitment | Sprint Planning | Sprint Planning | Construction commitment |
| Active development | Iterations in PI | Sprint execution | Parallel team sprints | Team sprints | Construction lifecycle |
| Integration control | System team and built-in quality | Shared Definition of Done | Nexus Integration Team | Scrum of Scrums coordination | Built-in quality |
| Deployment | Release on Demand | Continuous or sprint release | Integrated increment | Integrated product release | Transition phase |
| Monitoring and feedback | Inspect and Adapt | Sprint Review and Overall Retro | Nexus Sprint Review | Executive Action Team metrics | Enterprise awareness |
| Outcome measurement | Portfolio KPIs and OKRs | Empirical inspection | Integrated review feedback | Executive metrics | Continuous value measurement |
2. Governance Intensity¶
| Framework | Governance Layer | Standardization Level | Tailoring Flexibility |
|---|---|---|---|
| SAFe | High | High | Moderate |
| LeSS | Low | Low | Moderate |
| Nexus | Moderate | Moderate | Moderate |
| Scrum at Scale | Moderate | Moderate | High |
| Disciplined Agile | Variable | Variable | High |
3. Integration Approach¶
| Framework | Integration Strategy |
|---|---|
| SAFe | System team, architectural runway, PI sync |
| LeSS | Shared Definition of Done and feature teams |
| Nexus | Dedicated Nexus Integration Team |
| Scrum at Scale | Scrum of Scrums coordination |
| Disciplined Agile | Context-driven quality strategy |
4. Escalation Model¶
| Framework | Escalation Path |
|---|---|
| SAFe | ART to Portfolio governance |
| LeSS | Organizational simplification, minimal layers |
| Nexus | Integration team and Scrum roles |
| Scrum at Scale | Executive Action Team |
| Disciplined Agile | Enterprise awareness and decision forums |
5. Key Design Tradeoffs¶
- SAFe increases coordination predictability but adds governance overhead.
- LeSS minimizes overhead but requires strong product ownership.
- Nexus focuses on integration discipline.
- Scrum at Scale separates Product and Scrum cycles explicitly.
- Disciplined Agile emphasizes contextual tailoring.
Framework choice should align with organizational complexity, governance needs, and cultural maturity.