Velocity and Sprint Productivity

In every Scrum project, work is performed by the Scrum Team in short phases, known as Sprints. Each Sprint focuses on creating a usable product, ready to be implemented by the completion of the Sprint. Since each phase of the product development process is rife with challenges and problems, it can be difficult to determine just how much work will get done in each Sprint. To help manage the overall development process, the Team creates an estimate of the amount of work they plan on completing. This estimate is known as velocity.

Velocity Defined
Velocity is the sum of the features, attributes, and deliverable products the Scrum Team expects to create by the end of the Sprint. The estimate is much like a goal, giving the Scrum Team an idea of precisely what should be finished by the end of the Sprint in order for the product to meet the desired deliverable goal.

Is Velocity Firm?
Velocity is an estimate and may not reflect the actual work produced in each Sprint. It acts as a guideline for the Scrum Team, nothing more. Since teams are independent and may not always be under the direct supervision of a ScrumMaster, velocity allows them to develop a plan of attack to complete the project on time under ideal conditions.

Scrum is an agile process, meaning any issues or problems that arise during the sprint can be fixed on the fly rather than terminating the Sprint all together. As a result, the amount of work actually completed is dependent on the number of interruptions that occur during each Sprint. Remember, velocity is just a guideline and will likely fluctuate across different Scrum Teams and along different Sprints.

When implementing Scrum in your workplace, it is important to accept the agile nature of the management system. Change is acceptable as long as work is getting completed. To learn more about Scrum or to register to become a Certified ScrumMaster, contact us today.