Sprint Velocity Metrics

🚨 A Hard Truth: Without a Done Increment, velocity is ZERO. Think velocity is just tallying points? The truth: it only counts when those points become a Done, useful, valuable Increment in the Sprint. Here’s the definition straight from the Scrum.org glossary: Velocity: an optional, but often used, indication of the amount of Product Backlog turned into an Increment of product during a Sprint by a Scrum Team, tracked by the Developers for use within the Scrum Team. Too many teams misuse velocity. The story point accountants love to "claim" points to get credit for effort, even when the Increment isn’t in a usable state that provides potential value. Another trap: managers or stakeholders using velocity as a performance metric. Velocity is not a tool for comparison or reporting. It is strictly for the Scrum Team to forecast and plan. And it's optional and not required by Scrum! The Scrum Guide is crystal clear: the entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint. 👀 Miss that, and velocity is zero. In Scrum you are either Done or Not Done. 99% Done does not count. You are not Done if… ❌ "We completed everything and will get UAT signoff next month." ❌ "We are Done and will tackle code reviews next Sprint." ❌ "We are Done except for the technical debt, we will refactor later." ❌ "The feature is built, we are just waiting on integration testing." ❌ "It is ready once security does their review next month." What does Done mean? ✅ The PBI meets the team’s Definition of Done, with nothing left incomplete or deferred. ✅ The product Increment 📦 is both useful (someone could actually use it) and valuable (it provides a benefit to the business or users). I often get asked: "Should we get partial credit for story points?" ABSOLUTLEY NOT! Why? No PBI can be added to the product Increment unless it meets the Definition of Done. And if it’s not in the Increment, it doesn’t count. Which means your PBIs story points are not part of your velocity. Velocity might be useful for planning capacity, the capacity to get things Done. And if you are using velocity for release forecasting, you are not going to release a partially Done Increment, are you? Anything else is just fooling yourself. 🚨 If the Increment is not Done, transparency collapses. 👀 Stakeholders cannot inspect real progress. 📉 Release forecasting becomes fiction. The team may think they are moving forward, but without a usable Increment there is no progress to measure. 💬 If your Increment isn’t Done, why are you tracking velocity at all?

Pairing Velocity and Capacity Planning in Scrum Velocity is a common metric for sprint planning in Scrum. Teams typically use the average story points completed over the last several sprints to forecast future work. Let's set aside the "flaw of averages" (read my earlier post on using confidence intervals instead) and assume teams reading this post just use their average velocity. Relying solely on velocity can cause overcommitment when sprint durations fluctuate or team capacity changes. That's why capacity planning can complement velocity to improve planning accuracy. Pairing velocity with capacity planning creates a realistic, adaptable approach to sprint planning. Let's talk about why - and how - it works. Velocity Velocity measures the work a team delivers in a sprint, expressed in story points. It would be common for a team averaging 20 points to use that as a benchmark for future sprints. The risk is that velocity doesn’t adjust for sprint-specific factors like holidays or planned absences. That can lead to unrealistic commitments. Capacity (Availability) Capacity planning evaluates actual team availability for a specific sprint. It considers sprint length (e.g., 9 workdays instead of 10), planned absences (vacations, holidays, etc.), and working hours per developer. Team availability is converted into "developer-days." For example, a 5-person team working 8 hours daily for 10 days has 400 available hours max. Shorter sprints and absences reduce this capacity. Why Combine Velocity and Capacity? Realistic Commitments Velocity provides a stable benchmark, but capacity planning adjusts for unique sprint conditions. For example, if a team’s velocity is 20 points for a 10-day sprint, a 9-day sprint might lower this target by 10% to 18 points. Balanced Workloads Using velocity alone risks overcommitment. Using capacity alone risks underutilization. Combining them mitigates these risks and helps make commitments achievable. Adapting to Change Velocity anchors plans in proven performance (empiricism), but capacity planning accounts for variability (e.g., holidays, absences, onboarding, etc.). How to Pair Velocity with Capacity 1) Start with historical velocity as a baseline. 2) Calculate available developer-days, adjusting for holidays or absences within each sprint within the forecast timebox. 3) Scale back velocity to match capacity (e.g., if capacity is 90% of normal, reduce the velocity target by 10%). Benefits of Pairing Predictability: Commitments align with capacity for consistent delivery. Transparency: Stakeholders gain visibility into achievable goals. Flexibility: Teams adapt to sprint variations without risking outcomes. Deliver Predictably in Dynamic Conditions Velocity is a valuable metric but it doesn’t account for short-term variability. If calculating confidence intervals feels too complicated, then use capacity planning to fill the gap - creating a planning process that’s both empirical and adaptable.

Velocity in Scrum is one of the most misunderstood metrics - yet one of the most powerful when used correctly. At its core, Velocity represents the amount of work a Scrum Team can complete in a single Sprint, usually measured in Story Points. 📌 What Velocity Really Means Velocity = Total Story Points of all “Done” user stories in a Sprint (“Done” meaning completed and accepted - not half-finished work.) 🎯 Why Velocity Matters Velocity helps teams: • Forecast how much work they can commit to in future Sprints • Improve release planning and predictability • Increase transparency around team progress • Identify capacity trends over time 📘 Example If a team completes 40, 45, and 42 Story Points in three Sprints, their average velocity = ~42 Story Points per Sprint. This becomes a realistic reference point for planning the next Sprint. 🔑 Important Truths About Velocity ✔ Velocity is team-specific - it should never be compared across teams ✔ It stabilizes as the team matures ✔ It is not a KPI to judge performance ✔ It depends on team size, skills, complexity, and sprint duration ✔ It’s a planning tool, not a pressure tool Used wisely, Velocity helps teams plan with confidence. Used poorly, it creates fear and dysfunction. Scrum is about delivering value - not chasing numbers. Follow Sirisha Ch for more Scrum & Agile related interview prep. #Agile #Scrum #ScrumMaster #ProductOwner #AgileCoaching #AgileLeadership #SoftwareDevelopment #AgileMindset #ProductManagement #ContinuousImprovement #Innovation #AgileTeams #SprintPlanning #AgileDelivery #AgilePractices

📌 Understanding Capacity vs Velocity in Scrum — A Practical Guide One of the most common challenges in Agile teams is correctly calculating Capacity and Velocity before planning a sprint. These two metrics look similar, but they serve very different purposes. --- 🔹 What is Velocity? Velocity = Average story points completed by the team in previous sprints. It reflects team productivity and helps estimate future work. ✔ Based on past performance ✔ Calculated in story points ✔ Stable once the team matures ✔ Used for forecasting upcoming releases --- 🔹 What is Capacity? Capacity = Actual number of hours the team can commit in the upcoming sprint. It reflects team availability (not productivity). ✔ Based on the next sprint only ✔ Calculated in hours ✔ Changes due to leave, holidays, support load ✔ Used for accurate sprint planning --- 🔹 How to Calculate Sprint Capacity? Use the formula below: 1️⃣ Identify available team members e.g., 6 developers + 2 QA = 8 members 2️⃣ Deduct unavailable hours Leave, ceremonies, support work: 1 holiday → -8 hours Daily standup (0.5 hr × 10 days × 8 people) → -40 hours 2 team members on leave for 1 day → -16 hours 3️⃣ Calculate total workable hours Capacity = (Team Size × Work Hours × Sprint Days) – Deductions Example: 8 members × 8 hours × 10 days = 640 hours Deductions = 64 hours 👉 Final Capacity = 576 hours --- 🔹 The Difference (One Line Summary) 🔸 Velocity = What the team has done (story points) 🔸 Capacity = What the team can do (hours) --- 💬 Why It Matters Accurate capacity planning prevents: ✔ Over-commitment ✔ Under-utilization ✔ Burnout ✔ Rollovers ✔ Misaligned expectations A mature Agile team uses both metrics together to commit realistically. #Scrum #Agile #SprintPlanning #Velocity #CapacityPlanning #ProjectManagement #DeliveryExcellence #PMO