CAPM Practice: Determine how to plan project iterations

Velocity measures the team's throughput — how many story points (or other sizing units) the team completes per iteration. It is measured empirically over multiple sprints and used for forecasting: how much can be delivered in future sprints, and how many sprints will it take to complete the backlog. Velocity stabilizes as teams mature and is team-specific (cannot be compared across teams).

**Why not B:** Team satisfaction is measured through retrospectives and engagement surveys, not velocity. Velocity is a throughput metric measuring completed work, not a sentiment or morale indicator.

**Why not C:** Velocity is a team-level metric, not an individual one. Measuring individual speed contradicts agile principles of collective ownership and collaboration. Tracking individual performance can create unhealthy competition and discourage helping teammates.

**Why not D:** The rate at which items are added to the backlog measures backlog growth or product owner activity, not team throughput. Velocity specifically measures what the team delivers (completes), not what is requested or added.