SSM Introducing Scrum in SAFe Practice Question
An Agile Release Train (ART) is transitioning to SAFe. The Scrum Master notices that the team is struggling to align their local sprint goals with the overall Program Increment (PI) objectives. What is the most effective way for the Scrum Master to facilitate this alignment?
⚠ Common exam trap
Candidates frequently select administrative reporting options or wait for management to dictate alignment, missing that the Scrum Master actively facilitates mapping team work directly to PI objectives.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Facilitate a session to map team stories and iteration goals directly to PI objectives.
Effective alignment in SAFe requires the Scrum Master to coach the team on connecting their daily work to the broader PI objectives established during PI Planning. By ensuring the team understands how their stories contribute to the ART's business value, the Scrum Master fosters transparency and shared accountability. This alignment is critical because it ensures that autonomous Scrum teams remain synchronized with the train's strategic goals and deliver consistent value.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Mandate that the Product Owner dictates exactly how the team writes their iteration goals.
Why it's wrong here
Dictating iteration goals removes team autonomy and disempowers the Scrum team, which contradicts the core values of Scrum and SAFe. The team must own their goals to ensure high levels of commitment, and top-down mandates often result in lower quality and reduced engagement within the iterative cycle.
- ✗
Encourage the team to prioritize their own local technical debt tasks over PI objectives.
Why it's wrong here
Prioritizing local technical debt tasks over committed PI objectives undermines the train's predictability and value delivery. While managing technical debt is vital for long-term health, it should be balanced within the capacity allocation defined during PI planning to support the overall system and feature delivery goals.
- ✓
Facilitate a session to map team stories and iteration goals directly to PI objectives.
Why this is correct
Mapping team-level activities to PI objectives creates explicit visibility into the 'why' behind the work. This helps the team understand their specific contribution to the ART's success, reduces ambiguity, and ensures that every sprint increment is intentionally designed to support the broader program goals agreed upon during planning.
- ✗
Advise the team to ignore the PI objectives and focus solely on velocity metrics.
Why it's wrong here
Ignoring PI objectives in favor of velocity metrics is a counterproductive practice that ignores the value-delivery aspect of SAFe. Velocity is a measure of throughput, not business value, and focusing exclusively on it without context often leads to teams delivering work that does not satisfy the ART's mission.
About these practice questions
This SSM question is part of Courseiva's 385-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Scaled Agile exam blueprint
This SSM practice question is part of Courseiva's free Scaled Agile certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SSM exam.