| tag |
reason |
use |
Approvals |
SAFe uses Program Increment (PI) Planning events where objectives are agreed and approved by stakeholders. |
PI Planning |
Inspect and Adapt |
|
|
| tag |
reason |
use |
Automation |
SAFe promotes built-in quality through continuous integration and automated testing. |
Continuous Integration |
Built-in Quality |
|
|
| tag |
reason |
use |
Change Management |
SAFe manages change through structured backlogs and regular planning cadences. |
Program Backlog |
Enabler Stories |
|
|
| tag |
reason |
use |
Coordination Risk |
SAFe specifically addresses coordination across multiple teams through Agile Release Trains. |
Agile Release Train (ART) |
Scrum of Scrums |
|
|
| tag |
reason |
use |
Delegation |
SAFe emphasizes decentralized decision-making to empower teams. |
Decentralize Decision-Making |
|
|
| tag |
reason |
use |
Demo |
System Demos occur at the end of each iteration to show integrated work to stakeholders. |
System Demo |
Solution Demo |
|
|
| tag |
reason |
use |
Estimating |
SAFe uses story points and capacity-based planning during PI Planning. |
Story Points |
Capacity Allocation |
|
|
| tag |
reason |
use |
Issue Management |
SAFe uses program and team backlogs to track and prioritise work. |
Program Backlog |
Team Backlog |
|
|
| tag |
reason |
use |
Measurement |
SAFe measures progress through PI Objectives, velocity, and flow metrics. |
PI Objectives |
Flow Metrics |
Predictability Measure |
|
|
| tag |
reason |
use |
Meeting |
SAFe uses regular ceremonies including daily stand-ups, iteration planning, and PI Planning. |
PI Planning |
Daily Stand-up |
Iteration Planning |
|
|
| tag |
reason |
use |
Monitoring |
SAFe monitors progress through Program Boards, Kanban boards, and regular sync meetings. |
|
|
| tag |
reason |
use |
Prioritising |
SAFe uses Weighted Shortest Job First (WSJF) to prioritise work by economic value. |
WSJF |
Economic Prioritisation |
|
|
| tag |
reason |
use |
Release |
SAFe promotes continuous delivery through the Release on Demand capability. |
Release on Demand |
Continuous Delivery Pipeline |
|
|
| tag |
reason |
use |
Requirements Capture |
SAFe captures requirements as Features and Stories, refined through backlog grooming. |
Features |
User Stories |
Enablers |
|
|
| tag |
reason |
use |
Retrospectives |
SAFe includes Inspect and Adapt workshops for systematic improvement after each PI. |
Inspect and Adapt |
Iteration Retrospective |
|
|
| tag |
reason |
use |
Stakeholder Management |
SAFe engages stakeholders through Business Owners, Product Management, and regular demos. |
Business Owners |
Product Management |
|
|
| tag |
reason |
use |
Automated Testing |
SAFe emphasises built-in quality through test automation at all levels. |
Built-in Quality |
Test-First |
|
|