Project Management

TeamVelocity

Calculate and analyze team velocity for sprint planning. Track historical performance and predict future capacity.

Understanding Team VelocityA comprehensive guide to measuring and using velocity

What is Velocity?

Team Velocity is the amount of work (measured in story points) a Scrum team can complete during a single sprint. It's a fundamental metric in Agile project management that helps teams predict how much work they can realistically commit to in future sprints.

Why It Matters

Velocity matters because it enables teams to: 1) Plan sprints accurately - know how much work to commit, 2) Forecast delivery timelines - predict when features will be completed, 3) Identify trends - spot improving or declining team performance, 4) Optimize capacity - balance workload with team availability.

Avg Committed

35

Story Points Completed

33

Completion Rate

95%

Last 3 Avg

36

Volatility

9.9%

Velocity Range

10

P80 Capacity

31

Trend

+2.0

Velocity Trend

Velocity Trend Analysis

Sprint-by-Sprint Completion Rate

Sprint History

93%
91%
109%
89%
95%

Sprint Velocity Forecast

Higher simulations = more accurate forecasts

Conservative (P90)

31

90% confidence you can complete this

Recommended (P80)

34

80% confidence - safe commitment

Aggressive (P50)

39

50% confidence - stretch goal

Multi-Sprint Forecast

Cumulative Forecast

Forecast Details

SprintP50 (50%)P80 (80%)P90 (90%)Cumulative P80
Sprint 633302930
Sprint 733312961
Sprint 834312992
Sprint 9333129123
Sprint 10333129154
Sprint 11333129185

How Monte Carlo Forecasting Works

Monte Carlo simulation runs thousands of random scenarios using your historical velocity data. By sampling from your past sprint outcomes, it generates a probability distribution of possible future velocities. This reveals the likelihood of achieving different commitment levels - giving you scientific confidence in your forecasts.

P50: 50% chance of completingP80: 80% chance of completingP90: 90% chance of completing

Velocity Distribution

Cumulative Velocity

Sprint Performance Breakdown

Met/Exceeded (≥100%)
Close (80-99%)
Missed (<80%)

Velocity Glossary

Story Points

A unit of measure for expressing the overall effort required to implement a product backlog item. Points are relative - a 5-point item is roughly twice as much work as a 2-point item.

Team Velocity

The amount of work (in story points) a team can complete during a single sprint. Calculated by averaging completed points across multiple sprints.

Committed Points

The number of story points the team promises to deliver in a sprint. Based on capacity planning and historical performance.

Completed Points

Story points for work that is finished, tested, and ready for delivery. Only 'done' work counts toward velocity.

Completion Rate

Percentage of committed work actually completed. A rate above 100% indicates over-delivery; below 80% may signal capacity issues.

Volatility

How much velocity fluctuates between sprints, measured by coefficient of variation. Low volatility (<15%) means predictable delivery.

P80 Capacity

The number of story points you can commit to with 80% confidence. Recommended for sprint planning to ensure achievable goals.

Sprint Forecast

Predicting how many story points a team can complete in an upcoming sprint based on historical velocity data.

Sprint

A fixed time-box (usually 1-4 weeks) during which a specific set of work must be completed. Scrum teams typically run multiple sprints consecutively.

Scrum

An Agile framework for developing, delivering, and sustaining complex products. Emphasizes teamwork, accountability, and iterative progress toward well-defined goals.

Product Backlog

A prioritized list of features, functions, requirements, enhancements, and fixes that need to be delivered. The single source of work for the Scrum team.

Sprint Backlog

The set of product backlog items selected for the sprint plus the plan for delivering them. Owned by the development team.

Definition of Done

A shared understanding of what it means for work to be complete. Ensures transparency and quality. Typically includes criteria like code review, testing, and documentation.

Retrospective

A meeting held at the end of each sprint to reflect on what went well, what didn't, and how to improve. Key to continuous improvement.

Standup

A brief daily meeting where team members share progress, plans, and blockers. Helps identify impediments early.

Cumulative Flow Diagram

A visual chart showing the cumulative number of work items in different states over time. Helps identify bottlenecks and cycle time trends.

Cycle Time

The time from when a work item starts to when it's completed. Lower cycle time indicates faster delivery of value to customers.

Lead Time

The time from when a work item is requested to when it's delivered. Includes waiting time and is a key measure of overall delivery speed.

Throughput

The number of work items completed per time period. Like velocity but counts items (features, bugs) rather than story points.

Monte Carlo Forecast

A forecasting method that uses random sampling to simulate thousands of possible outcomes. Provides probability distributions for more accurate predictions than simple averages.

Percentile (P50, P80, P90)

Statistical measures indicating the value below which a percentage of observations fall. P80 means 80% of outcomes are at or below that value - used for confidence in planning.

Confidence Interval

A range of values that's likely to contain the true value. In velocity forecasting, it shows the range where your actual velocity will likely fall.

Forecast Horizon

The number of future sprints you're predicting. Longer horizons have more uncertainty. 3-6 sprints is typically the practical limit for reliable forecasting.

Velocity Trend

The direction and rate of change in velocity over time. Positive trend = improving, negative = declining. Used to adjust forecasts for team trajectory.

Standard Deviation

A measure of how spread out velocity values are from the average. High standard deviation means unpredictable delivery; low means consistent performance.

Coefficient of Variation

Standard deviation divided by mean, expressed as percentage. Useful for comparing volatility across teams with different average velocities.

Scope Forecasting

Predicting how much work (in story points) can be completed over a specific time period. Used for release planning and commitment setting.

Commitment Velocity

The number of story points a team commits to deliver in a sprint. Should be based on forecast data, not wishful thinking.