What is meant by the velocity of the team?

Question

Options

• AThe rate a team puts in a normal work day.
• BThe rate at which features are released to the customer.
• CThe rate at which the team completes the work.
• DThe rate at which the team renews itself.

• B
  5% (2)
• C
  93% (38)
• D
  2% (1)

Explanation

Velocity in an Agile/Scrum context measures how much work a team completes in a given iteration (sprint), making C correct - it captures the team's throughput of work items (typically story points or tasks) over time.

Why the distractors are wrong:

• A is wrong because velocity isn't about hours worked in a day - it measures output, not effort or attendance.
• B is close but wrong - releasing features to customers is about deployment frequency or throughput to production, not velocity, which is an internal planning metric.
• D is wrong - team renewal (turnover/onboarding) is a team health metric, unrelated to velocity.

Memory tip: Think of velocity like a car's speedometer - it tells you how fast you're covering ground (work), not how long you drove, where you delivered, or who's in the car.

No community discussion yet for this question.