Velocity in Scrum, actually

In Scrum it is considered a good idea for teams to know about the progress they have been making. It can be one parameter (of several) to take into account when considering the inherently uncertain future. Teams often use ‘Velocity’ as an indicator of progress. As the term is not even mentioned in the Scrum Guide we’d better consider carefully how to apply it in accordance with Scrum’s foundational principles.

In complex and uncertain environments, more is unknown than is known. There is much we don’t know. What we know is subject to change. Only what we have achieved is known (unless we prefer to cover up). Progress is in what we have done, more than in what we plan to do. What we plan to do are assumptions that need validation by emerging actions and decisions. We make and incrementally change decisions based on what is known.

In Scrum it is considered a good idea for teams to know about the progress they have been making. It is one parameter (of several) to take into account when considering the inherently uncertain future.

From the Scrum Guide (“Sprint Planning”):

The input to this meeting is the Product Backlog, the latest product Increment, projected capacity of the Development Team during the Sprint, and past performance of the Development Team.