SAFe Scrum Master 5.0 Study Guide
2022/2023
1. Agile frameworks:
SAFe Scrum
Crystal
Kanba
n
eXtreme Programming
(XP) Feature-driven
development
2. What does a Scrum Master do?: - Servant leaders and coaches for an
Agile Team.
- Help educate team in Scrum, XP, Kanban and SAFe, ensuring the
agreed Agile process is being followed.
- Help remove impediments and foster an environment for high-
performing team dynamics, continuous flow and relentless
improvement.
- Facilitates team events
- Works with RTE to ensure train meets PI objectives
- Fosters normalized estimating within the team
,- Assists the PO in backlog for PI and IP.
- Attends scrum of scrum meetings.
3. Scrum Master Responsibilities: Exhibits lean-agile
leadership Supports the team rules
Facilitates the team's progress toward
team goals Leads team efforts in relentless
improvement Facilitates meetings
Supports the PO
Eliminates
impediments
Promotes SAFe quality
practices Builds a high-
performing team Protects
and communicates
Responsibilities on the train
Coordinates with other
teams
Facilitates preparation and readiness for ART
events Supports estimating
4. ART: Agile Release Train
5. PO: Product Owner
6. Program Increment (PI) Planning: A cadence-based, face-to-face event
that serves as the heartbeat of the Agile Release Train (ART), aligning
all the teams on the ART to a common mission and vision.
,7. Innovation and Planning Iteration: Occurs every PI and serves multiple
pur- poses. It acts as an estimating buffer for meeting PI objectives, as
well as providing dedicated time for innovation, continuing education,
and PI planning and Inspect and Adapt (I&A) events.
8. Inspect & Adapt (I&A): A significant event, held at the end of each PI,
where the current state of the solution is demonstrated and evaluated
by the train. Teams reflect and identify improvement backlog items via
a structured, problem-solving workshop
9. Iteration: A basic building block of Agile development. Each is a
standard, fixed-length timebox, where Agile Teams deliver
incremental value in the form of working, tested software and
systems.
Cycle - Defines, builds, integrates, & test.
10.What is the recommended timebox duration for an Iteration?: 2
weeks; however, 1-4 weeks is acceptable, depending on the
business context.
11.Who participates in the Inspect & Adapt (I&A) phase?: All
stakeholders, including:
1.The Agile Teams
2. Release Train Engineer (RTE)
3. System and Solution Architect Engineering
4. Product Management, Business Owners, and others on the Train
12.What results from the I&A phase?: Improvement backlog items that
, go to the Program Backlog for the next PI Planning event
13.3 parts of I&A: PI System
Demo Quantitative
Measurement
Retrospective and Problem-Solving Workshop
14.Purpose of PI System Demo: To show all the Features the ART has
devel- oped over the course of the PI
Leads: PM, PO, System Team
Attend: BO, Stakehlders, PM, RTE, SM & Teams
15.PI System Demo Timebox: ~1 hr or less
16.What is one primary measurement to be considered in quantitative met-
rics?: Program predictability measure
Updated end of inspect & adapt event
17.Retrospective goal: To identify whatever issues they would like to
address
2022/2023
1. Agile frameworks:
SAFe Scrum
Crystal
Kanba
n
eXtreme Programming
(XP) Feature-driven
development
2. What does a Scrum Master do?: - Servant leaders and coaches for an
Agile Team.
- Help educate team in Scrum, XP, Kanban and SAFe, ensuring the
agreed Agile process is being followed.
- Help remove impediments and foster an environment for high-
performing team dynamics, continuous flow and relentless
improvement.
- Facilitates team events
- Works with RTE to ensure train meets PI objectives
- Fosters normalized estimating within the team
,- Assists the PO in backlog for PI and IP.
- Attends scrum of scrum meetings.
3. Scrum Master Responsibilities: Exhibits lean-agile
leadership Supports the team rules
Facilitates the team's progress toward
team goals Leads team efforts in relentless
improvement Facilitates meetings
Supports the PO
Eliminates
impediments
Promotes SAFe quality
practices Builds a high-
performing team Protects
and communicates
Responsibilities on the train
Coordinates with other
teams
Facilitates preparation and readiness for ART
events Supports estimating
4. ART: Agile Release Train
5. PO: Product Owner
6. Program Increment (PI) Planning: A cadence-based, face-to-face event
that serves as the heartbeat of the Agile Release Train (ART), aligning
all the teams on the ART to a common mission and vision.
,7. Innovation and Planning Iteration: Occurs every PI and serves multiple
pur- poses. It acts as an estimating buffer for meeting PI objectives, as
well as providing dedicated time for innovation, continuing education,
and PI planning and Inspect and Adapt (I&A) events.
8. Inspect & Adapt (I&A): A significant event, held at the end of each PI,
where the current state of the solution is demonstrated and evaluated
by the train. Teams reflect and identify improvement backlog items via
a structured, problem-solving workshop
9. Iteration: A basic building block of Agile development. Each is a
standard, fixed-length timebox, where Agile Teams deliver
incremental value in the form of working, tested software and
systems.
Cycle - Defines, builds, integrates, & test.
10.What is the recommended timebox duration for an Iteration?: 2
weeks; however, 1-4 weeks is acceptable, depending on the
business context.
11.Who participates in the Inspect & Adapt (I&A) phase?: All
stakeholders, including:
1.The Agile Teams
2. Release Train Engineer (RTE)
3. System and Solution Architect Engineering
4. Product Management, Business Owners, and others on the Train
12.What results from the I&A phase?: Improvement backlog items that
, go to the Program Backlog for the next PI Planning event
13.3 parts of I&A: PI System
Demo Quantitative
Measurement
Retrospective and Problem-Solving Workshop
14.Purpose of PI System Demo: To show all the Features the ART has
devel- oped over the course of the PI
Leads: PM, PO, System Team
Attend: BO, Stakehlders, PM, RTE, SM & Teams
15.PI System Demo Timebox: ~1 hr or less
16.What is one primary measurement to be considered in quantitative met-
rics?: Program predictability measure
Updated end of inspect & adapt event
17.Retrospective goal: To identify whatever issues they would like to
address
