Course contentsShow
← Software Engineering
Lesson 1656 of 1,93348. Project Management for EngineersFree lesson

Velocity and Capacity Planning

Track team velocity over sprints to forecast delivery timelines based on historical throughput.

Velocity and Capacity Planning

You'll learn: How to track team velocity over sprints to forecast delivery timelines based on historical throughput.

The Core Idea

Velocity is the measure of how much work your team actually completes in a sprint, typically expressed in story points. Capacity planning uses this historical velocity data to predict when future work will be done.

Think of it like tracking your car's fuel efficiency. After several road trips, you notice you consistently get 30 miles per gallon. Now when planning a 300-mile journey, you can confidently predict you'll need about 10 gallons. Similarly, if your team consistently completes 40 story points per sprint, you can forecast that a 120-point feature will take roughly 3 sprints.

Tracking Velocity

Record your team's completed story points at the end of each sprint. After 3-5 sprints, calculate the average velocity. This becomes your planning baseline.

For example:

  • Sprint 1: 35 points
  • Sprint 2: 42 points
  • Sprint 3: 38 points
  • Sprint 4: 44 points
  • Average velocity: ~40 points/sprint

Using Velocity for Forecasting

To forecast delivery timelines:

  1. Sum the story points for your planned work
  2. Divide by your average velocity
  3. Add a buffer for the cone of uncertainty

If your product backlog has 200 points of prioritized work and your velocity is 40 points/sprint, you're looking at approximately 5 sprints (200 ÷ 40 = 5).

Capacity vs Velocity

Capacity is theoretical—how much work your team could do. Velocity is empirical—what they actually deliver. Always plan with velocity, not capacity.

Key Takeaway: Velocity transforms historical throughput into a predictable planning tool, letting you forecast timelines with data rather than guesswork.