← Back to The Checklist

At the end of each iteration, the team adds their individual effort estimates associated with user story that was completed during that iteration. This total is called velocity. It’s so easy. 🙄

Mathing (no, not a real word)

Table of Contents

We need only to do a math story problem to understand the how (no trains involved).

<aside> ✏️ 25 points remain, and we can complete 5 points in a single iteration. Math it: $25/5=5$


As each sprint comes to an end, the process should be repeated to calculate the team’s current velocity. If there seems to be a drastic swing either up or down, consider the following:

Estimating (Sizing)

There are different ways to estimate the size of your story. Here are two common ways it’s done. It doesn’t matter what you use, so long as it agrees with what each estimation “point” represents (difficulty, unknowns, time, etc.).

T-shirt Method

While the t-shirt method is easy to use, inexperienced teams may have difficulty determining how to represent their estimation(s) in sizing. That said, practice makes perfect. The longer the team uses it or works together, the more relatable the sizing will be with the actual tasks. The sizing, with their number represented for velocity purposes, are:


‘ol fashion numbers

Much like the above, we’re relating our choices to the amount of work based on how complex, unknown, time, etc., the task(s) will be. You can use any number system you want. However, I recommend sticking with single digits or their x10 equivalents. For example,