SSM Supporting ART Events Practice Question
In a large Agile Release Train, the System Demo is often attended by various stakeholders. Why is it important for the Scrum Master to ensure the team is prepared for this event every two weeks?
⚠ Common exam trap
A common trap is thinking the System Demo is optional if the team hasn't finished a 'big' feature. In SAFe, the demo must happen every iteration to show the integrated state, even if progress is small.
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
✓
To provide objective evidence of progress and get stakeholder feedback
The System Demo is the primary mechanism for receiving objective feedback on the integrated system. If the team is not prepared, they lose the opportunity to validate their work against stakeholder expectations. Regular demos ensure that any misalignments are caught early, reducing the risk of a significant 'miss' at the end of the PI.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
To allow the team to practice their public speaking and presentation skills
Why it's wrong here
While public speaking may be a secondary benefit, it is not the primary purpose of the System Demo. The focus is on obtaining objective feedback on the working software to ensure that the train is moving in the right direction and meeting the needs of the stakeholders.
- ✓
To provide objective evidence of progress and get stakeholder feedback
Why this is correct
Objective evidence is a core principle of SAFe. By showing working, integrated software, the team proves progress in a way that status reports cannot. Stakeholder feedback at this stage is invaluable for making small course corrections before they become expensive and time-consuming problems later.
- ✗
To ensure the team has a reason to complete their stories before the deadline
Why it's wrong here
The System Demo should not be used as a 'deadline' to pressure teams. Instead, it should be a natural outcome of the iteration's work. Using it as a pressure tactic can lead to poor quality and technical debt, which ultimately harms the train's long-term velocity and stability.
- ✗
To give the Scrum Master a chance to demonstrate the team's velocity
Why it's wrong here
Stakeholders are generally interested in the 'what' (the product) rather than the 'how much' (velocity). Velocity is a team-internal metric. Showing it at a System Demo can lead to inappropriate comparisons between teams and takes the focus away from the actual value being delivered.
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.