SAFE AGILE ADVANCED SCRUM MASTER
EXAM 2026 EXAMINATION TEST
◉ What are the Business Owner's responsibilities in the ART?'.
Answer: The key stakeholders on the Agile Release Train
◉ What is the ART program vision?. Answer: Expresses strategic
intent, may be expressed in a variety of forms.
◉ What is the ART roadmap. Answer: Series of features and planned
release dates. commitment is made only to the next release.
Subsequent releases are best estimates.
◉ What is the function of features in the program backlog?. Answer:
Features are those behaviors of the system that directly fulfill some
user need.
◉ What do the estimates in the program backlog mean?. Answer:
They are only estimates and do not imply committed delivery
◉ What is the key driver for the Team backlog?. Answer: Program
priorities
,◉ What are Spikes?. Answer: Could be technical spikes or functional
spikes. Can be used for analysis, design out to try to type an idea.
Spikes are demonstrable like any other story and included in the
demo
◉ What does a story point represent?. Answer: Single number for
volume, complexity, knowledge, uncertainty
◉ Is ART cadence without synchronization enough?. Answer: No.
Synchronize with cadenence to assure delivery.
◉ Does ART value follow organizational silos?. Answer: No. ART is
based on cross-functional, self organized teams that define, build
and test a feature to deliver value
◉ What is estimating poker?. Answer: Estimating poker combines
expert opinion, analogy, and disaggregation for quick but reliable
estimates
◉ Who are included in estimating poker?. Answer: Team members.
The PO participates but does not estimate
◉ What are the benefits of estimating in the team?. Answer:
Increases accuracy by including all perspectives, builds
understanding, creates shared commitment
,◉ Who should not create estimates for the team backlog?. Answer:
Managers, Architect, Select Group
◉ What is normalized estimation?. Answer: Normalized story point
estimating provides the economic basis for estimating work within
and across programs
◉ Are defects estimated?. Answer: Yes. Defects are included in the
team backlog
◉ What is release planning?. Answer: Cadence based release
planning meetings are the pacemaker of the Agile Enterprise
◉ How often is release planning done for ART?. Answer: Every 8-12
weeks
◉ How long is the release planning meeting for ART?. Answer: Two
days
◉ Who owns the feature priorities in the ART release planning?.
Answer: Program Management
, ◉ Who owns the story planning and high level estimates in the ART
release planning?. Answer: Development team
◉ Who are the intermediaries for governance, interfaces, and
dependencies in the ART release planning?. Answer: Architects and
UX
◉ What is the result of the ART release planning meeting?. Answer:
A committed set of program objectives for the next PI
◉ What are the inputs to the ART release planning process?.
Answer: Vision and top ten features
◉ What are the outputs from the ART release planning process?.
Answer: Team and PI objectives, and program board
◉ What does the program board visualize?. Answer: Program board
visualizes Features, WIP, dependencies divided into sprints by team
◉ What are objectives?. Answer: Brief summaries in business terms
of what each team intends to deliver in the upcoming PI
◉ How can we align to a mission in the release planning?. Answer:
Using PI objectives we can align to a mission
EXAM 2026 EXAMINATION TEST
◉ What are the Business Owner's responsibilities in the ART?'.
Answer: The key stakeholders on the Agile Release Train
◉ What is the ART program vision?. Answer: Expresses strategic
intent, may be expressed in a variety of forms.
◉ What is the ART roadmap. Answer: Series of features and planned
release dates. commitment is made only to the next release.
Subsequent releases are best estimates.
◉ What is the function of features in the program backlog?. Answer:
Features are those behaviors of the system that directly fulfill some
user need.
◉ What do the estimates in the program backlog mean?. Answer:
They are only estimates and do not imply committed delivery
◉ What is the key driver for the Team backlog?. Answer: Program
priorities
,◉ What are Spikes?. Answer: Could be technical spikes or functional
spikes. Can be used for analysis, design out to try to type an idea.
Spikes are demonstrable like any other story and included in the
demo
◉ What does a story point represent?. Answer: Single number for
volume, complexity, knowledge, uncertainty
◉ Is ART cadence without synchronization enough?. Answer: No.
Synchronize with cadenence to assure delivery.
◉ Does ART value follow organizational silos?. Answer: No. ART is
based on cross-functional, self organized teams that define, build
and test a feature to deliver value
◉ What is estimating poker?. Answer: Estimating poker combines
expert opinion, analogy, and disaggregation for quick but reliable
estimates
◉ Who are included in estimating poker?. Answer: Team members.
The PO participates but does not estimate
◉ What are the benefits of estimating in the team?. Answer:
Increases accuracy by including all perspectives, builds
understanding, creates shared commitment
,◉ Who should not create estimates for the team backlog?. Answer:
Managers, Architect, Select Group
◉ What is normalized estimation?. Answer: Normalized story point
estimating provides the economic basis for estimating work within
and across programs
◉ Are defects estimated?. Answer: Yes. Defects are included in the
team backlog
◉ What is release planning?. Answer: Cadence based release
planning meetings are the pacemaker of the Agile Enterprise
◉ How often is release planning done for ART?. Answer: Every 8-12
weeks
◉ How long is the release planning meeting for ART?. Answer: Two
days
◉ Who owns the feature priorities in the ART release planning?.
Answer: Program Management
, ◉ Who owns the story planning and high level estimates in the ART
release planning?. Answer: Development team
◉ Who are the intermediaries for governance, interfaces, and
dependencies in the ART release planning?. Answer: Architects and
UX
◉ What is the result of the ART release planning meeting?. Answer:
A committed set of program objectives for the next PI
◉ What are the inputs to the ART release planning process?.
Answer: Vision and top ten features
◉ What are the outputs from the ART release planning process?.
Answer: Team and PI objectives, and program board
◉ What does the program board visualize?. Answer: Program board
visualizes Features, WIP, dependencies divided into sprints by team
◉ What are objectives?. Answer: Brief summaries in business terms
of what each team intends to deliver in the upcoming PI
◉ How can we align to a mission in the release planning?. Answer:
Using PI objectives we can align to a mission
