Courseiva
Introducing Scrum in SAFe →mediumMultiple Choice

SSM Introducing Scrum in SAFe Practice Question

A newly formed Scrum Team inside an Agile Release Train has just held its first Iteration Planning event. The Scrum Master notices the team is building a detailed, task-level plan for the entire Program Increment and treating it as a commitment to be tracked daily. What should the Scrum Master do to align the team with Scrum as practiced in SAFe?

⚠ Common exam trap

The trap here is assuming that because SAFe plans in Program Increments, the team's commitment horizon must also stretch to the whole PI.

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

✓

Coach the team that the Iteration is the planning horizon for team-level commitment, while the PI Objectives and team PI plan represent the broader forecast they refine with their Product Owner and during the Inspect and Adapt workshop.

Within SAFe, the Iteration remains the team's commitment horizon, while the Program Increment is a forecast captured through team PI Objectives. Keeping the detailed, committable plan at the Iteration level and refining the PI plan with the Product Owner and during the Inspect and Adapt workshop preserves Scrum's empirical control while fitting the train's cadence.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    Instruct the team to abandon Iteration Planning and instead generate all User Stories for the Program Increment up front so the plan is stable for the whole train.

    Why it's wrong here

    Abandoning Iteration Planning removes the team's ability to replan every two weeks and adapt to what was learned, which contradicts Scrum's empirical approach. SAFe expects teams to plan their own workload each Iteration during Iteration Planning, refining backlog items that were identified at PI Planning, so freezing a full PI of stories up front undermines flexibility.

  • ✗

    Have the team stop using Iteration Goals and instead report only against PI Objectives at the end of each Iteration so leadership has consistent metrics.

    Why it's wrong here

    Iteration Goals are a core Scrum in SAFe practice that align the team each Iteration and feed the team's PI Objectives; removing them eliminates a key alignment and transparency mechanism. Reporting solely against PI Objectives at every Iteration skips the two-week inspect-and-adapt loop and confuses the PI forecast with Iteration-level commitment.

  • ✓

    Coach the team that the Iteration is the planning horizon for team-level commitment, while the PI Objectives and team PI plan represent the broader forecast they refine with their Product Owner and during the Inspect and Adapt workshop.

    Why this is correct

    Scrum in SAFe keeps the Iteration as the team's commitment horizon, while the Program Increment is a forecast expressed through team PI Objectives planned at PI Planning. Coaching the team to plan workload at the Iteration level and treat the broader PI plan as an adjustable forecast aligns with how SAFe defines team planning cadence and commitment.

  • ✗

    Advise the team to make the Program Increment plan a firm commitment and escalate any deviation to the Release Train Engineer during the daily Scrum of Scrums.

    Why it's wrong here

    Treating the PI plan as a firm commitment with escalation for every deviation misrepresents SAFe, which frames the PI as a forecast that teams adjust through the Iteration cadence and review at the Inspect and Adapt workshop. Escalating normal replanning to the Release Train Engineer would also bypass the team's own self-management and the Product Owner's role in prioritization.

About these practice questions

One of 385 original SSM practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

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.