SAFe Scrum Master Study Guide 5.0
Study online at https://quizlet.com/_hus6xf
1. Agile frameworks: SAFe
Scrum
Crystal
Kanban
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
, SAFe Scrum Master Study Guide 5.0
Study online at https://quizlet.com/_hus6xf
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 purposes. 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 developed 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 metrics?-
: Program predictability measure
Updated end of inspect & adapt event
, SAFe Scrum Master Study Guide 5.0
Study online at https://quizlet.com/_hus6xf
17. Retrospective goal: To identify whatever issues they would like to address
18. Retrospective objective: To identify a few significant problems that the teams can potentially address -
What went well, what didn't go well, what can do better next time.
19. PDCA Cycle: Plan
Do
Check
Adjust
20. Who facilitates the PI Planning event?: Release Train Engineer (RTE)
21. In which iteration does PI Planning take place?: Innovation and Planning Iteration
22. __ ________ is essential to SAFe; if you are not doing it, you are not doing
SAFe.: PI Planning
23. Business Benefits of PI Planning: Establishing face-to-face communication across all team mem-
bers and stakeholders
Building the social network the ART depends on
Aligning development to business goals with the business context, Vision, and team project PI objectives
Identifying dependencies and fostering cross-team and cross-ART collaboratio
Providing the opportunity for "just the right amount of architecture and Lean User Experience (UX) guidance)
Matching demand to capacity, eliminating excess WIP
Fast decision-making
24. PI Planning Inputs: Business context
Roadmap and vision
Top 10 features of the Program Backlog
NFRs (Non-functional Requirements)
25. PI Planning Outputs: Committed PI objectives (A set of SMART objectives that are created by each team
with the business value assigned by the Business Owners)
Program board (this highlights the new feature delivery dates, feature dependencies among teams and with other ARTs,
and relevant milestones)
Plan is the goal
26. 3 Areas of Preparation for a Successful PI Planning: Organizational Readiness
Content Readiness
Facility Readiness
27. Organizational Readiness: Strategic alignment and teams trains setup
Study online at https://quizlet.com/_hus6xf
1. Agile frameworks: SAFe
Scrum
Crystal
Kanban
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
, SAFe Scrum Master Study Guide 5.0
Study online at https://quizlet.com/_hus6xf
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 purposes. 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 developed 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 metrics?-
: Program predictability measure
Updated end of inspect & adapt event
, SAFe Scrum Master Study Guide 5.0
Study online at https://quizlet.com/_hus6xf
17. Retrospective goal: To identify whatever issues they would like to address
18. Retrospective objective: To identify a few significant problems that the teams can potentially address -
What went well, what didn't go well, what can do better next time.
19. PDCA Cycle: Plan
Do
Check
Adjust
20. Who facilitates the PI Planning event?: Release Train Engineer (RTE)
21. In which iteration does PI Planning take place?: Innovation and Planning Iteration
22. __ ________ is essential to SAFe; if you are not doing it, you are not doing
SAFe.: PI Planning
23. Business Benefits of PI Planning: Establishing face-to-face communication across all team mem-
bers and stakeholders
Building the social network the ART depends on
Aligning development to business goals with the business context, Vision, and team project PI objectives
Identifying dependencies and fostering cross-team and cross-ART collaboratio
Providing the opportunity for "just the right amount of architecture and Lean User Experience (UX) guidance)
Matching demand to capacity, eliminating excess WIP
Fast decision-making
24. PI Planning Inputs: Business context
Roadmap and vision
Top 10 features of the Program Backlog
NFRs (Non-functional Requirements)
25. PI Planning Outputs: Committed PI objectives (A set of SMART objectives that are created by each team
with the business value assigned by the Business Owners)
Program board (this highlights the new feature delivery dates, feature dependencies among teams and with other ARTs,
and relevant milestones)
Plan is the goal
26. 3 Areas of Preparation for a Successful PI Planning: Organizational Readiness
Content Readiness
Facility Readiness
27. Organizational Readiness: Strategic alignment and teams trains setup
