Velocity is a good measure of team performance.

Question

Options

• ATrue
• BFalse

• A
  15% (7)
• B
  85% (41)

Explanation

B is correct because velocity measures the amount of work a team completes per sprint, not the quality or value delivered. A team can inflate velocity by breaking stories into smaller pieces, taking on easier work, or cutting corners on quality - all without actually improving performance.

Why A is wrong: Velocity is a planning and forecasting tool, not a performance benchmark. Using it as a performance metric creates perverse incentives - teams optimize for points rather than delivering real value to customers. Agile frameworks explicitly warn against this misuse.

Memory tip: Think of velocity like a car's odometer - it tells you how far you've gone, not how well you drove. A team racing through low-value features records high velocity but delivers poor performance. Real performance is measured by outcomes (customer satisfaction, business value delivered), not output.

No community discussion yet for this question.