Scaled Agile Framework (SAFe)
Fund value streams, not projects.
SAFe is the world's most widely adopted framework for scaling Agile across large organizations. Developed by Dean Leffingwell, it organizes teams of 50–125 people into Agile Release Trains aligned to value streams, operating on synchronized 10-week Program Increments with PI Planning, WSJF prioritization, and Lean Portfolio Management. This skill is built for practitioners already working inside SAFe — Release Train Engineers, Product Managers, Agile coaches, and portfolio leaders who need a working operating model, not introductory Agile concepts.
“We have our first PI Planning in 3 weeks. We have 6 teams, about 70 people total. Nobody knows what's supposed to happen on Day 1 and our RTE is…”
Turn 50 teams into one ART — run PI Planning, prioritize with WSJF, and fund value streams instead of projects
SAFe organizes large organizations into Agile Release Trains (ARTs) — stable teams of 50–125 people aligned to a shared value stream. ARTs operate on a 10-week Program Increment (PI) cadence: five 2-week development sprints plus one Innovation & Planning (IP) sprint. Every PI begins with PI Planning — a 2-day big-room event where all teams jointly build PI Objectives, map cross-team dependencies on the Program Board, and ROAM risks as Resolved, Owned, Accepted, or Mitigated. Prioritization across the backlog uses WSJF (Weighted Shortest Job First: Cost of Delay ÷ Job Size) to rank Features and Epics by business value delivered per unit of time invested. At the portfolio level, Lean Portfolio Management (LPM) replaces project-based funding with value stream budgets, governed by a Portfolio Kanban with Epic hypothesis statements and Lean Budget guardrails. The PI closes with an Inspect & Adapt event combining a System Demo, PI metrics review, and a structured Problem-Solving Workshop using fishbone diagrams and an improvement backlog.
Most organizations succeed with Agile at the team level — sprints complete, stories ship, Scrum ceremonies run. The crisis hits at scale: teams can't align on cross-team dependencies, product roadmaps have no enterprise prioritization logic, and annual project-based funding destroys the flow that Agile teams worked to achieve. SAFe exists to solve the coordination and governance failures that Scrum was never designed to handle.
Apply the most prescriptive and actionable parts of SAFe — PI Planning facilitation, WSJF prioritization, Program Board ROAM, and Lean Budget design — with a coach who knows the exact roles, timeboxes, artifacts, and failure modes of every ceremony.
- Your ART composition — number of teams, team names, and headcount
- A list of Features or Epics you need to prioritize (for WSJF analysis)
- Your current organizational structure — value streams, portfolios, and funding model
- Specific SAFe ceremony challenges — e.g., a PI Planning that lost momentum, an Inspect & Adapt that produced no improvement backlog, or a Program Board with unROAMed risks
- A PI Planning agenda with team breakout scripts, timebox guides, and facilitation interventions for the most common failure modes
- A WSJF-ranked Feature list with Cost of Delay component scores, job-size estimates, and a prioritization rationale you can present to stakeholders
- An ART Launch Readiness scorecard across organizational, team, and leadership dimensions with a sequenced preparation checklist
- A Lean Portfolio Management design with Portfolio Kanban state definitions, Epic hypothesis statement templates, and Lean Budget guardrail recommendations
Watch the methodology work.
Three specimens from a single real session: the same situation, unaided and calibrated, the full transcript, and the skill answering live in the channel where the work happens.
“Your 6-team ART is 3 weeks from its first PI Planning. The Program Backlog has 200 items with no prioritization logic. Product Managers don't know which Features to present or how to defend their choices. The RTE has never facilitated a 2-day big-room event and isn't sure what 'team breakouts' actually means in practice. Leadership is asking what the tangible output of PI Planning will be and whether it's worth taking 70 people offline for 2 days.”
“You walk into PI Planning with 15 WSJF-scored Features ready for team consumption, a scripted 2-day agenda with timebox calls, and a Program Board pre-loaded with team swim lanes. Day 1 produces draft PI Objectives from all 6 teams and a Program Board showing every cross-team dependency with ROAM status. Day 2 closes with committed PI Objectives, a fully ROAMed risk board, and a confidence vote of 4.1/5. Leadership receives a PI Objectives table with Business Owner-scored business value they can read without knowing what a story point is.”
The same skill, where the work happens.
No new app to learn. The methodology runs over the WhatsApp Business API, so the answer lands as a reply in the thread you’re already in — same rigour, zero context-switch.
What it does, specifically.
Each capability is a distinct move drawn straight from the source methodology — not a generic assistant guessing.
PI Planning Facilitation
Walk through the complete 2-day PI Planning event — from pre-PI prep and Business Context presentation through team breakouts, dependency identification, risk ROAMing, and final PI Objective commitment. Get facilitation scripts, timebox guides, and specific interventions for common breakdowns such as teams in 'fake planning,' dependency avoidance, and uncommitted stretch objectives.
WSJF Feature Prioritization
Apply the Weighted Shortest Job First formula — Cost of Delay (User/Business Value + Time Criticality + Risk Reduction/Opportunity Enablement) divided by Job Size — to rank your Program Backlog Features or Portfolio Epics. Work through each cost-of-delay component for specific features and produce a relative priority sequence grounded in business value economics rather than stakeholder opinion or loudest voice.
ART Launch Readiness Assessment
Evaluate organizational readiness to launch an Agile Release Train across four dimensions: leadership alignment, value stream clarity, team formation, and tooling/environment readiness. Identify blockers and sequence the preparation steps — from value stream identification through RTE selection and team topology design — to arrive at PI Planning ready.
Lean Portfolio Management Design
Design or improve your Lean Portfolio Management implementation: define Portfolio Kanban funnel, analysis, backlog, implementing, and done states; create Epic hypothesis statement templates with measurable outcomes; establish Lean Budget guardrails per value stream; and set up the Portfolio Sync cadence and Epic Owner accountability model to replace project-based governance.
Program Board Dependency ROAM
Build and work a Program Board — the artifact that makes cross-team dependencies visible across the full PI. Apply the ROAM framework (Resolved, Owned, Accepted, Mitigated) to each identified risk and dependency, ensuring every critical dependency leaves PI Planning with a named owner, a resolution status, and a mitigation action.
Graded before it shipped.
Every skill is scored against independent scenarios for methodology fidelity before it goes live — not vibes, a rubric.
PI Objectives Table
Structured team-level and ART-level PI Objectives, each with a business value score (1–10 Fibonacci), committed/stretch designation, and measurable acceptance criteria — the official commitment output of PI Planning that leadership can read without knowing what a story point is.
WSJF Priority Matrix
A ranked Feature list showing User/Business Value, Time Criticality, Risk Reduction/OE scores, Job Size estimates, and computed WSJF scores — ready to sequence your Program Backlog for the upcoming PI with an economics-based rationale for each prioritization decision.
ART Launch Readiness Scorecard
A dimension-by-dimension assessment of organizational readiness to launch an Agile Release Train, with red/yellow/green status per dimension, blockers identified, and a sequenced preparation checklist covering leadership alignment, value stream definition, team formation, and tooling.
Program Board Dependency Map
A sprint-by-sprint dependency visualization across all ART teams, with each inter-team dependency annotated with its ROAM status (Resolved/Owned/Accepted/Mitigated), the accountable team, and the resolution or mitigation action — built during PI Planning and maintained at ART Sync.
Grounded in the original work.
Every answer traces back to a real source and the practitioner who wrote it — not a secondhand summary. Here is the source of record.
Dean Leffingwell
Dean Leffingwell is the creator of the Scaled Agile Framework (SAFe) and Chief Methodologist at Scaled Agile, Inc. He authored 'Scaling Software Agility' (2007) and 'Agile Software Requirements' (2011), and has spent decades building the framework documentation, role guides, and certification curriculum that now serve thousands of enterprises globally. SAFe is deployed at more than half of the Fortune 100 and supports one of the largest Agile certification ecosystems in the world, spanning SP, SPC, RTE, PO/PM, and LPM credentials.
Scaled Agile Framework (SAFe) — scaledagile.com
Creator of SAFe; Chief Methodologist at Scaled Agile, Inc.; author of 'Scaling Software Agility' (2007) and 'Agile Software Requirements' (2011); framework deployed at thousands of global enterprises including a majority of the Fortune 100.
Be first to run it.
Scaled Agile Framework (SAFe) is being built right now. Leave your email and we’ll tell you the moment it goes live.