The scrum master for a large project must provide an estimate of what can be delivered in six months. What should the scrum master do?

Question

Options

• ACommit to a specific feature set for delivery
• BExplain that a commitment will be provided after planning
• CHave the team estimate in story points to commit to a specific set of features
• DUse the team's historical velocity to calculate a range of features that can be delivered

• A
  5% (1)
• B
  5% (1)
• C
  15% (3)
• D
  75% (15)

Explanation

Long-range estimates in agile are best expressed as a range based on empirical data - specifically the team's historical velocity. By calculating velocity over past iterations and projecting it forward, the scrum master can provide a realistic, defensible range of features rather than a false-precision commitment. Option A (commit to specific features) creates a fixed-scope promise that ignores agile's embrace of change and uncertainty. Option B (wait until after planning) is unhelpful when a high-level forecast is legitimately needed by stakeholders. Option C (estimate in story points to commit to a specific set) is too rigid - velocity-based ranges account for variability and are more honest about uncertainty.

No community discussion yet for this question.