They were able to complete only seven out of nine which adds up to 42 story points. Step 2: Find the Mean or AverageAll that has to be done is to add up the total of completed story points, and divide by the number of sprints. Sprint 1: 5 user stories x 6 story points = 30 Sprint 2: 6 user stories x 6 story points = 36 Sprint 3: 7 user stories x 6 story points = 42 Total = 96 So, your average sprint velocity is 108 ÷ 3 = 36. Future velocity can be calculated based on this figure. This means that they completed 30 story points. During sprint 2: The team made a commitment to completing seven user stories, which included the one that was previously left incomplete. Again, each story was estimated at six story points, which made a total of 42 story points. They were able to complete six, which adds up to 36 story points. During sprint 3: The team made a commitment to completing nine user stories. Each story was estimated at six story points, which made a total of 54 story points. However, one of the story points was not completed. Any incomplete story points are moved to the next sprint. Let’s assume that… During sprint 1: The team made a commitment to completing six user stories. Each story was estimated at six story points, which made a total of 36 story points. The number of story points that were successfully completed is summed up. A good average would require a review of at least three sprints. This example uses story points for the estimate. Step 1: Make a Note of Story Points Completed During the Sprint Once a sprint is completed, the team sits together for the Sprint Review event. If a team is new, the velocity for the first sprint is roughly calculated during the first sprint and is fine-tuned and rendered more accurate during subsequent sprints. Here, we will show you how velocity can be calculated, provided all other parameters stay constant. Typically, velocity is calculated based on the work that has previously been done. If the team members change over the course of the project, which ideally should not happen (but at times cannot be helped), the velocity will change. They could decide to have story points in multiples of 10 instead of multiples of 1 say 10, 20 and so on. Story points need to take into consideration how complex a task is, how much risk and uncertainty there is around it, and the amount of work required to complete entirely. How Can Velocity Be Estimated?Each Scrum team has its own velocity, which is based on the individual capacities of each team member. Story points are ratios, which are decided by the team, and should be in whole numbers for easy handling. Story points are relative for example, a story that is assigned a 2 should have approximately twice the complexity or should take twice the time estimated for a story point with the value 1. – Mike Cohn, Mountain Goat SoftwareStory points in Agile measure the effort and time it will take to complete a user story, or any other piece of work. Story Points for User Stories: What Are They, and How Are They Used?Story points are estimates of effort as influenced by the amount of work, complexity, risk and uncertainty. All that is mentioned is that estimates should happen, and the nitty gritty of how, exactly, it is done is left to each team to decide for themselves. The Product Owner uses the velocity calculation as a rough estimate to determine how many sprints will be needed to finish all the PBIs that are in the Product Backlog, and to achieve an MVP (Minimum Viable Product) that is ready to be shipped. Here’s an interesting point to note! While most Scrum teams estimate velocities using user stories, story points and burndown charts, the Scrum Guide itself does not have much to say on the subject. Scruminc As a key performance indicator, the velocity measures the speed of a development team, and is an indicator of the average amount of PBIs (Product Backlog Items) or User Stories that can be completed during a sprint. Release Planning is done based on the team’s predicted velocity. Velocity is calculated at the end of the Sprint by totalling the Points for all fully completed User Stories. Sprint VelocityVelocity is a measure of the amount of work a Team can tackle during a single Sprint and is the key metric in Scrum. It can be used to work out time estimates during the planning process, and helps the teams to track and improve their efficiency over time.In this article, you will understand what sprint velocity is, how it is calculated, and how the team can track their progress using a velocity chart. By Susan May The velocity is a simple, yet very important metric that Scrum teams use to predict how much work can be actually completed within a sprint.