SSM Supporting ART Events Practice Question

Answer analysis

Option-by-option breakdown

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

• ✗

  Re-estimate all remaining backlog items to ensure the team's velocity forecast is accurate.

  Why it's wrong here

  Re-estimating the entire remaining backlog before every Scrum of Scrums is not a prerequisite and would be wasteful. Estimation happens during backlog refinement and iteration planning, not as preparation for a coordination meeting. Velocity forecasting is a team-level concern and does not need to be recalculated for the Scrum of Scrums.

• ✓

  Identify dependencies on other teams and note any that are at risk of affecting delivery this iteration.

  Why this is correct

  Dependencies are a core topic at the Scrum of Scrums because they are where cross-team coordination happens. Preparing a clear list of current and at-risk dependencies lets the team contribute meaningfully and helps the ART adjust before delivery is impacted. Without this preparation, dependency issues surface too late to be addressed effectively within the iteration.

• ✗

  Prepare a demonstration of the team's latest feature for stakeholders attending the Scrum of Scrums.

  Why it's wrong here

  Demos belong to the System Demo, not the Scrum of Scrums. The Scrum of Scrums is a short coordination meeting among team representatives, not a stakeholder demonstration event. Preparing a demo would misallocate effort and confuse the purpose of the meeting, which is to synchronize work and resolve cross-team issues.

• ✓

  Review the team's progress against its iteration goals and identify any impediments that need outside help.

  Why this is correct

  The Scrum of Scrums is where teams coordinate and raise impediments that require cross-team action. Before attending, the team should assess progress toward its iteration goals and surface blockers it cannot resolve alone. This preparation makes the Scrum of Scrums productive and ensures the team brings actionable information rather than a vague status update.

• ✗

  Complete a full root-cause analysis of every defect found during the iteration.

  Why it's wrong here

  Root-cause analysis of all defects is excessive for Scrum of Scrums preparation and belongs in retrospectives or problem-solving workshops. The Scrum of Scrums focuses on coordination, dependencies, and cross-team impediments, not deep defect analysis. Bringing exhaustive defect analysis would consume the meeting's time and distract from its coordination purpose.