Scrum Metrics Formulas:
From: | To: |
Capacity represents the total amount of work a Scrum team can handle in a sprint, measured in story points. Velocity measures the average amount of work a team completes during a sprint, helping predict future performance.
The calculator uses these Scrum metrics formulas:
Where:
Explanation: Capacity helps teams plan how much work they can commit to, while velocity helps track performance over time and improve sprint planning accuracy.
Details: Tracking capacity and velocity is essential for effective sprint planning, identifying team performance trends, and making realistic commitments for future sprints.
Tips: Enter available hours, hours per point, completed story points, and number of sprints. All values must be positive numbers to get accurate calculations.
Q1: What's the difference between capacity and velocity?
A: Capacity is the estimated work a team can handle, while velocity is the actual work completed. Capacity is used for planning, velocity for measurement.
Q2: How often should velocity be measured?
A: Velocity should be tracked at the end of each sprint to establish a reliable average over 3-5 sprints for accurate forecasting.
Q3: What factors affect team capacity?
A: Team size, individual availability, holidays, meetings, and other non-development activities all impact team capacity.
Q4: Can velocity be compared between different teams?
A: No, velocity is team-specific and should not be used to compare different teams as story point estimation varies between teams.
Q5: How can teams improve their velocity?
A: Teams can improve velocity by reducing technical debt, improving collaboration, refining estimation techniques, and minimizing interruptions.