SAFe 6.

0 Events
Scaled Agile Framework
 SAFe 6.0 Events
SAFe Events on different SAFe Levels

Team Level:
Iteration Planning, Team Sync(Daily Stand Up),
Iteration review, Iteration retrospective Pre- and Post-PI Planning, Solution Demo

AL
Rest :

LA
I
ART (Program) Level: ESSENTIAL LEVELS

NT

RG
PI Planning, ART Sync - Coach Sync (SoS) & PO

SE

E
Sync, System Demo, Inspect and Adapt

ES
workshop SAFe
LEVELS
PO
RT

LL
Lean Budget Review, Communities of It includes all Events from:
F

FU
Practice, Portfolio Sync, Roadshow OL ESSENTIAL LEVELS
IO PORTFOLIO LEVEL
Rest : LARGE SOLUTION LEVEL
ESSENTIAL LEVELS
 SAFe Events – Team level
u Iteration Planning : This is team level event, in which agile team forecast which stories
from team backlog can be completed during the Iteration, and form a plan to deliver
them along with agreed Iteration goal.

u Team Sync (Daily stand up) : This is 15 mins timeboxed event held at same time and
place each day to discuss progress towards their iteration goal and make a plan for next
24 hours.

u Iteration Review: The team demonstrate the stories completed during the iteration and
gather feedback from PO, customers, business owners and other stakeholders.

u Iteration Retrospective: In this event, the agile team identify and agree to implement,
potential improvements to their processes, practices and team working agreements
 SAFe Events – ART(Program) level
u PI Planning : Its is a ART level 2 day event, where everyone in the ART gets together to agree
team and overall PI objectives. Teams select the features based on priority from ART backlog
and map to the Iterations in the PI. In PI Planning, dependencies between teams are identified,
while risks are identified and either resolved, owned, accepted or mitigated.

u ART Sync – Coach Sync (Scrum of Scrum) and PO Sync:

Coach sync facilitated by RTE, and SM participates to discuss progress and open Impediments
and/or dependency.
In PO Sync call, Product Manager, PO and other selected stakeholders discuss progress,
priorities and scope adjustment.

u System Demo: After end of each Iteration, Integrated work is demonstrated to business owners
and other stakeholders.
 SAFe Events – ART(Program) level
Inspect and Adapt workshop:
It is in the last Iteration of the PI and is made up of three parts: the PI system demo;
quantitative and qualitative measurement; and the problem-solving workshop.

u The PI System demo is similar to the System demo but it show the current state of the solution,
highlighting the work done throughout the whole PI, not just in the last iteration. Also, the entire ART
(the members of every team) is invited and many of these people will not have been to the System
demos.

u Quantitative and Qualitative Measurement part, the RTE presents ART metrics to the members of the
ART. One key metrics is program predictability measure, Each team’s planned vs. actual business value
is rolled up to create the program predictability measure.

u Retrospective & Problem-solving workshop, The team runs brief (30 mins or less) retrospective, the
goal is to identify a few significant issues they would like to address during the problem-solving
workshop. The focus is to identify improvement items, teams conduct a relatively short meeting to
identify the root causes of problems and identify actions that can address the root cause of the
problems.
 SAFe Events – Large Solution
u Pre- and Post-PI Planning
In order to coordinate work across multiple ARTs and also with suppliers, vendors, there is an
alignment meeting both before and after the individual ART PI planning sessions. Synchronisation of
the PI planning events is essential in order for the pre- and post-PI planning events to be meaningful
and happen within a few days of each other.

u Solution Demo
During the event, capabilities, features are demonstrated. During the solution demo, the development
efforts of the solution train (multiple ARTs and work from suppliers) are made visible to customers and
other stakeholders and Solution Train gathers the feedback. It is an opportunity for the customer and
other stakeholders to influence upcoming work.
Participants for Solution Demo: Solution train engineer (STE), Customers, Stakeholders,
representatives from each of the ART (e.g. product managers and product owners), Solution
management, Lean portfolio management (if used).
 SAFe Events – Portfolio level
u Lean Budget Review
It is generally twice a year, Its a periodic review of how the portfolio budget is distributed across the
different value streams. This could be done using a technique such as participatory budgeting where the LPM
collaborate with business owners and other stakeholder to agree how much budget is needed to run the
business and how much remains in order to grow the business.

u Communities of Practice
The Value management office (VMO-previously APMO) can supports communities of practice for RTEs and
STEs, and scrum masters, to help sharing of ideas across the portfolio.

u Portfolio Sync
The VMO or LPM stakeholders may facilitate this event. The purpose of which is to see how well the portfolio
is progressing towards meeting strategic objectives. Topics typically include reviewing epic implementation,
the status of KPIs, addressing dependencies and removing impediments. This should be no more frequent
than every two weeks.

u Roadshow
It is an enterprise level demonstration of work completed across multiple solution trains. This will help in
getting feedback and input, ahead of a lean budget review event.
Thank you
Scaled Agile Framework