SAFe Implementation Roadmap: Steps, 12-Month Plan and Example
10 min read ยท 2026-10-25
The SAFe Implementation Roadmap is the sequence of steps the Scaled Agile Framework recommends for adopting SAFe in an organization: build a coalition for change, train change agents and leaders, organize around value, launch a first Agile Release Train (ART), coach it, then extend to more trains and the portfolio. The current version on the framework site lists 13 steps, from Reaching the Tipping Point to Accelerate.
The steps tell you what to do, not when or who. This guide turns them into a 12-month plan with six phases, owners and checkable milestones, so a transformation lead, agile coach, PMO head or Release Train Engineer can run it and report on it. It includes a filled-in example, the metrics to report and the traps that turn SAFe rollouts into training programs with no change in delivery.
The roadmap at a glance
Goal: Within 12 months, one Agile Release Train has run at least two Planning Intervals (PIs) with its business owners, results are measured against a baseline, and leadership has approved the next trains and portfolio changes. Duration: 12 months
Build the case and the change team (Weeks 1-6)
Agree on why the organization is changing and set up the people who will lead the change.
- Write the reason for change in business terms, such as slow delivery across teams or missed commitments to customers (Reaching the Tipping Point).
- Name an executive sponsor and agree on two or three outcomes the change must deliver.
- Train a first group of change agents, usually as SAFe Practice Consultants (Train Lean-Agile Change Agents).
- Set up a Lean-Agile Center of Excellence (LACE) with a lead, a small core team and a backlog of its own.
Milestone: A signed one-page case for change, a named sponsor and a LACE with members and a first backlog.
Align leaders (Weeks 5-10)
Give executives and managers a shared understanding of the new way of working and their role in it.
- Run leadership training for executives, managers and future business owners (Train Executives, Managers, and Leaders).
- Agree on what leaders will do differently, such as attending PI Planning and reviewing system demos (Lead in the Digital Age).
- Identify decisions that must change, such as how funding and staffing are approved.
- Measure a baseline for delivery and business outcomes before anything changes.
Milestone: Key leaders trained, a list of leadership commitments agreed, and a baseline report on delivery and outcomes.
Organize around value and plan (Weeks 9-14)
Decide where to start and write the implementation plan.
- Map operational value streams (how the business delivers value to customers) and the development value streams that support them (Organize Around Value).
- Design the first ART: which teams, systems and people it needs to deliver end to end.
- Pick the first ART where the business need is clear and leaders are committed.
- Write the implementation plan with dates, roles, training and launch steps (Create the Implementation Plan).
Milestone: A value stream map, a first ART design with named teams, and an implementation plan approved by the sponsor.
Prepare and launch the first ART (Weeks 14-22)
Get the train ready and run its first PI Planning.
- Fill the key roles: Release Train Engineer, Product Management, System Architect and business owners (Prepare for ART Launch).
- Prepare the ART backlog with features that have a clear benefit hypothesis and acceptance criteria.
- Train all teams on the train together, then run the first PI Planning event (Train Teams and Launch ART).
- Publish the PI objectives and the ART planning board so dependencies and dates are visible.
Milestone: First PI Planning held, with committed PI objectives approved by business owners and an ART planning board in place.
Coach the ART through two PIs (Weeks 22-44)
Help the train deliver and improve, PI by PI.
- Coach teams, the RTE and Product Management during iterations, system demos and ART syncs (Coach ART Execution).
- Hold the Inspect and Adapt event at the end of each PI and turn the top problems into improvement items.
- Run the second PI Planning with lessons from the first.
- Report progress to the sponsor against the baseline after each PI.
Milestone: Two PIs completed with Inspect and Adapt held, and a results report shared with leadership.
Expand and improve the portfolio (Weeks 40-52)
Decide how far to extend SAFe and start changing portfolio practices.
- Choose and prepare the next ARTs based on what the first train learned (Launch More ARTs and Value Streams).
- Start Lean Portfolio Management practices, such as a portfolio Kanban and participatory budgeting, where they fit (Enhance the Portfolio).
- Move ownership of coaching and training to the LACE and internal coaches (Accelerate).
- Write next year's implementation roadmap with the sponsor.
Milestone: Next ARTs selected with launch dates, first portfolio practices running and next year's plan approved.
The 13 steps in plain terms
The framework presents the roadmap as a visual and a series of articles, one per step. The steps below are from the current version on the framework's site. Earlier versions grouped some of them differently, so confirm the list for the version your organization uses.
The steps are not strict gates. Leadership training often overlaps with value stream work, and a second train can prepare while the first is still being coached. Use the order as a default.
- 1. Reaching the Tipping Point: a clear, shared reason to change, and a leader willing to sponsor it.
- 2. Train Lean-Agile Change Agents: a group of people who can teach and coach SAFe inside the company.
- 3. Create a Lean-Agile Center of Excellence: a small team that runs the change as its own product.
- 4. Train Executives, Managers, and Leaders: leaders learn the model and their new responsibilities.
- 5. Lead in the Digital Age: leaders change how they act, decide and support teams.
- 6. Organize Around Value: map value streams and design ARTs around them.
- 7. Create the Implementation Plan: dates, roles, training and launch steps for the first trains.
- 8. Prepare for ART Launch: roles filled, backlog ready, logistics planned.
- 9. Train Teams and Launch ART: team training and the first PI Planning.
- 10. Coach ART Execution: support the train through its first increments.
- 11. Launch More ARTs and Value Streams: repeat with the next trains.
- 12. Enhance the Portfolio: align strategy, funding and governance with the new structure.
- 13. Accelerate: keep improving and make the change self-sustaining.
Example: a first-year roadmap for a bank's digital channels
Picture a retail bank where web, mobile and payments teams work in separate projects, and new features need four teams to coordinate by email. The chief digital officer sponsors the change. The first ART covers digital onboarding, from the app screens to the account opening back end.
Each quarter has an owner and a milestone that can be checked. Notice that the sponsor's main job is in the first two quarters: committing leaders and freeing people for the first train.
- Q1 (owners: chief digital officer and LACE lead): case for change, eight change agents trained, LACE set up, leadership training for twenty managers. Milestone: baseline report and leadership commitments signed.
- Q2 (owners: LACE lead and enterprise architect): value stream workshop, onboarding ART designed with nine teams, RTE and product manager appointed. Milestone: first PI Planning held with committed objectives.
- Q3 (owners: RTE and agile coaches): first PI executed with system demos every two weeks, Inspect and Adapt held. Milestone: PI objectives reviewed with business owners, improvement backlog agreed.
- Q4 (owners: RTE, LACE lead and finance partner): second PI, payments ART prepared, a portfolio Kanban started for digital investments. Milestone: year-one results shown to the executive committee and next year's plan approved.
Who owns what
A SAFe rollout fails when it is owned only by coaches. The framework is built around business owners and leaders who take part in planning and reviews. Name each role with a person in your implementation plan, and make sure each has time for it, not just a title.
The LACE should work like a team with its own backlog, priorities and review rhythm. It owns the implementation roadmap and reports to the sponsor.
- Executive sponsor: owns the case for change, removes blockers and holds leaders to their commitments.
- LACE lead: owns the implementation roadmap, training plan and reporting.
- Change agents (SPCs) and agile coaches: train and coach leaders, teams and ART roles.
- Release Train Engineer: runs the ART's events, tracks dependencies and risks, and leads improvement.
- Product Management: owns the ART backlog and feature priorities with business owners.
- System Architect: guides technical design across teams on the train.
- Business owners: approve PI objectives, attend PI Planning and system demos, and judge value delivered.
- Scrum Masters or team coaches and Product Owners: run the work at team level.
Metrics to track
Measure a baseline before the first train launches, or you will not be able to show results. The framework groups measures into three areas: outcomes (is the business getting results), flow (how well work moves through the system) and competency (how well people and teams apply the practices). Report a few from each, not dozens.
Avoid comparing velocity between teams. It is a team planning tool, not a performance score, and using it to rank teams will distort the numbers.
- Business outcomes: the two or three outcomes in the case for change, such as time from idea to customer release or onboarding completion rate.
- PI predictability: business value achieved against business value planned in PI objectives, scored by business owners.
- Flow time: time from a feature entering the backlog to its release, from Jira, Azure DevOps or your tracking tool.
- Flow load: number of features in progress at once, which should go down as focus improves.
- Competency: results of the framework's self-assessments, repeated each PI.
- Engagement: a short team survey each PI on clarity, workload and confidence in the plan.
How to present it to leadership
Executives do not need the framework diagram. They need to know what problem you are solving, what changes for them and what results to expect when. Use one slide with the six phases as a timeline, the first ART named on it, and three markers: first PI Planning, end of the second PI and the expansion decision.
Be explicit about what you need from them: attendance at PI Planning and system demos, decisions on funding and staffing for the first train, and protection for teams during the first PI. Report results after each PI against the baseline, including what did not improve. Leave out training numbers as a success measure. Trained people are an input, not a result.
How to adapt the roadmap
A smaller organization with one product and fewer than a dozen teams can often use a single ART and a lighter configuration. Combine the first three phases, keep value stream mapping short and focus on getting the first PI Planning right. Most portfolio steps can wait until there is more than one train.
Large or regulated organizations should plan more time for organizing around value and for governance changes, because funding, compliance and audit processes often assume project-based work. Bring risk, compliance and finance into the LACE early, and confirm with them which controls and documents must stay in place. If two or more trains share major systems, plan their launch dates so their PI Planning events can be aligned.
Common mistakes to avoid
- Treating the rollout as a training program produces certified people and unchanged delivery, so tie every phase to a business outcome and measure it against a baseline.
- Launching a train before its backlog and roles are ready makes the first PI Planning chaotic, so fill key roles and prepare features with clear acceptance criteria first.
- Skipping leadership training leaves managers working the old way around the new structure, so train leaders before teams and agree on what they will do differently.
- Launching several trains at once spreads coaches too thin, so prove the model with one train for two PIs before expanding.
- Designing ARTs around existing departments keeps the hand-offs you wanted to remove, so organize trains around value streams that deliver end to end.
- Letting the LACE work without authority stalls decisions, so give it a sponsor, a backlog and a regular review with leadership.
Frequently asked questions
What is the SAFe Implementation Roadmap?
It is the ordered set of steps the Scaled Agile Framework recommends for adopting SAFe, from building a reason to change through launching Agile Release Trains to extending the approach to the portfolio. The current version lists 13 steps. Organizations turn it into their own plan with dates, owners and milestones.
How long does a SAFe implementation take?
Launching and stabilizing a first Agile Release Train often takes several months, including leadership training, preparation and at least two PIs. Extending to more trains and the portfolio usually spans one or more years. The pace depends on the size of the organization and how quickly leaders commit.
What is an Agile Release Train?
An Agile Release Train is a long-lived team of agile teams that plans, builds and delivers together around a shared mission and backlog. It plans in Planning Intervals (called Program Increments in earlier versions), which typically last 8 to 12 weeks. The train is led by a Release Train Engineer, Product Management and a System Architect.
Who leads a SAFe implementation?
An executive sponsor owns the change, and a Lean-Agile Center of Excellence runs it day to day. Change agents, often SAFe Practice Consultants, train and coach leaders and teams. Business owners and the Release Train Engineer lead each train.
What is the difference between the SAFe Implementation Roadmap and a SAFe roadmap?
The Implementation Roadmap is the plan for adopting the framework itself. A roadmap inside SAFe is a delivery plan for a train or a portfolio, showing the features and milestones planned for the next few PIs. You need the first to set up the structure that produces the second.