Unable to meet a sprint's committed velocity, an agile team approaches the agile coach to define the next sprint's velocity. What should the agile coach advise?

Question

Options

• ASplit each story into multiple stories to meet the desired velocity.
• BSet the velocity to the delivered story points of the last sprint.
• CUse different estimation methods for stories and defects to meet the desired velocity.
• DRe-estimate by assigning more story points to smaller stories to increase the velocity.

• A
  5% (1)
• B
  73% (16)
• C
  14% (3)
• D
  9% (2)

Explanation

Velocity should reflect actual, empirical performance - not a manipulated target. Using the delivered story points from the last sprint as the basis for the next sprint's planned velocity is honest, realistic, and prevents teams from over-committing again. Splitting stories (A) or re-estimating with inflated points (D) artificially game the metric without improving actual throughput. Using different estimation methods for defects vs. stories (C) adds inconsistency and undermines the reliability of velocity as a planning tool.

No community discussion yet for this question.