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.

• ✓

  The team is committing to more PI Objectives than it can realistically deliver given its capacity and dependencies.

  Why this is correct

  If the team meets iteration goals but misses PI Objectives, the likely cause is overcommitment at the PI level. The team may be accepting too many features or underestimating dependencies and risks. The Scrum Master should facilitate a root-cause analysis on how PI Objectives are set and whether capacity and dependencies are accurately reflected during planning.

• ✗

  The team is not conducting daily stand-ups effectively, leading to poor coordination.

  Why it's wrong here

  Ineffective stand-ups would typically affect iteration execution and goal completion. Since the team meets iteration goals, daily coordination is probably sufficient. The predictability drop is at the PI level, pointing to planning and commitment issues rather than daily execution.

• ✗

  The team is not using the Program Board to track dependencies, causing integration delays.

  Why it's wrong here

  While dependency tracking is important, the symptom of meeting iteration goals but missing PI Objectives is more directly linked to overcommitment at the PI level. Integration delays would likely also impact iteration goals. The root cause is more likely in how PI Objectives are selected and sized.

• ✗

  The team is not breaking down features into stories small enough to fit within an iteration.

  Why it's wrong here

  The team meets its iteration goals, so story sizing is likely adequate. The issue emerges at the PI level, where committed PI Objectives are not being met despite iteration success. This suggests a disconnect between iteration execution and PI planning commitments, not a story-sizing problem.