SSM Supporting ART Events Practice Question
A Scrum Master is preparing for the team's first PI Planning. The team has never created PI Objectives before. What guidance should the Scrum Master provide?
⚠ Common exam trap
Test-takers frequently confuse PI Objectives with a detailed user story list or treating them as private team artifacts rather than shared business value statements.
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
✓
PI Objectives should describe the business value the team intends to deliver in the PI, and each should have a planned business value assigned.
PI Objectives communicate the business value a team intends to deliver during the PI and are assigned planned business values. They are created collaboratively, shared transparently, and are not a detailed story list. The other options misrepresent their purpose, audience, or authorship.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
PI Objectives should describe the business value the team intends to deliver in the PI, and each should have a planned business value assigned.
Why this is correct
PI Objectives summarize the business and technical goals the team intends to achieve in the PI. Assigning a business value from 1 to 10 helps the team and stakeholders understand relative importance and supports the ART in assessing planned versus actual value.
- ✗
PI Objectives should be a detailed list of every user story the team will complete in the PI.
Why it's wrong here
PI Objectives are higher-level summaries of intended value, not a detailed story list. Listing every user story would obscure the business outcomes and make it harder for stakeholders to understand the team's commitments and for the ART to measure value delivery.
- ✗
PI Objectives should be written only by the Product Owner without team input.
Why it's wrong here
PI Objectives are created collaboratively by the team during PI Planning, often with input from the Product Owner and stakeholders. Writing them alone removes team ownership and may not reflect the team's technical understanding, capacity, and commitments.
- ✗
PI Objectives should be kept private to the team and not shared with stakeholders.
Why it's wrong here
PI Objectives are shared transparently with the ART and stakeholders during the draft plan review and final plan review. Keeping them private prevents alignment, hides dependencies, and undermines the purpose of PI Planning as a collaborative, transparent event.
About these practice questions
Courseiva writes every SSM question from scratch — 385 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.