Skip to content
CAPMHard

CAPM Practice: Determine how to document project controls for an adaptive project

Question 11 of 60 in Determine how to document project controls for an adaptive project

Pick an answer below — you'll get the explanation instantly, no signup.

An adaptive team tracks velocity for 8 sprints. The velocity varies significantly: 28, 45, 33, 51, 27, 44, 38, 29. The product owner wants to use the highest velocity (51) for release planning. What is the BEST advice?
Show answer & explanation

Correct answer: Use the average (approximately 37) with an acknowledgment of high variability, and plan for a range of release dates rather than a single date

Explanation

High velocity variability (27-51) makes single-point forecasting unreliable. Using the average (≈37) with acknowledgment of the observed range provides the most honest planning basis. Release planning should express a range of completion dates (best case at 51/sprint, expected at 37/sprint, conservative at 27/sprint) rather than a single optimistic date. The root cause of high variability (sprint composition, team disruptions, story sizing inconsistency) should also be investigated to stabilize performance.

Key Concept

This question covers Determine how to document project controls for an adaptive project under Determine how to document project controls for an adaptive project (Agile Frameworks/Methodologies).

Share:

All 1,500+ CAPM questions are free

Sign up to track your progress, see detailed analytics, and get personalized study recommendations.

Sign Up Free