Skip to main content

Velocity in Agile Projects

This article talks about calculating the team velocity of the agile project and addressing the benefit of the team velocity.

Velocity is an extremely simple, powerful method for accurately measuring the rate at which teams consistently deliver business value. 

It is a measure of how much product backlog items the team can complete in the given amount of time.

It is used the compare the iterations for the given team on a given project, the note is only completed work counts for calculating the velocity.

Before you begin to calculate your team’s velocity, you will want to complete at least three to five sprints.

This allows for a team that is new to Agile project management to get used to the workflow and for any changes the team is going through to normalize.

Your velocity will fluctuate during these initial sprints but will stabilize after three or more have been completed. 

Agile velocity formula:

Sprint 4:

Planned = 8 user stories * 3 story points = 24 story points

Actual = 4 user stories * 3 story points = 12 story points

Sprint 5:

Planned = 10 user stories * 5 story points = 50 story points

Actual = 7 user stories * 5 story points = 35 story points

Sprint 6:

Planned = 9 user stories * 4 story points = 36 story points

Actual = 7 user stories * 4 story points = 28 story points

Average sprint velocity = (sum of all sprint actual story points)/ number of sprints

Average sprint velocity = (sum of all sprint actual story points)/ number of sprints

Average sprint velocity = (12+35+28)/3 = 25

The average sprint velocity is 25, from the Sprint 7 Scrum owner can plan to complete 25 worth of user story point work.

Some of the benefits of velocities are:
  • Understanding about agile project performance
  • Reporting project progress, productivity, predictability
  • Finding pain points and improvement areas
  • Used as metrics
  • Calculating the rate at which the product moving forward
  • Provides vision what can be achieved in next release
Kindly note that keep on increasing the team velocity is not mean to maximize the productivity, when we focus more on increasing the team velocity the team may skip following standards, unit testing, bug-fixing. The goal is to maintain the optimum velocity over time, which takes account of following standards, quality and other factors.

Comments

Post a Comment

Popular posts from this blog

Certified Enterprise Architect Professional (CEAP) - Module 4 - Architecture Precursors

 Architecture Precursors: Precursors to modern Enterprise Architecture (EA) include early frameworks like IBM's Business Systems Planning (BSP), which focused on aligning business strategy with information systems, as well as other Information Systems (IS) architecture methodologies that emerged in the 1970s and 80s, emphasizing the connection between business processes and IT systems, laying the groundwork for the holistic view of an organization that EA represents today; the "Master Plan for Information Systems" by Evans and Hague is also considered a foundational concept in this area. Drivers: internal / external pressure enforce to change the system Aims & Directives: Aims:  Goals Objectives Requirements Directives: Principles (example: Principles can be associated with business, data, applications, infrastructure, or security) Policies (example: Members of the public have minimal access to data) Business Rules (example: A rule directs and restricts a procedure)
Post a Comment
Read more

Scaled Agile Framework (SAFe)

The Scaled Agile Framework (SAFe) is a set of organizational and workflow patterns for implementing agile practices at an enterprise scale. The framework is a body of knowledge that includes structured guidance on roles and responsibilities, how to plan and manage the work, and values to uphold. Scrum is a simple, flexible approach to adopting Agile that's great for small teams. SAFe is an enterprise-wide Agile framework designed to help bring Agile beyond the team and into the company as a whole. Scaled Agile has built a comprehensive level that includes all the four layers called the team, program, large solutions, and portfolio level. 4 Layers: Portfolio - Strategy, Vision, Roadmap, Strategy goal, Decision making, Budget, Portfolio level metrics,  Program - Align multiple teams towards a common mission, Bring together all the Agile teams, transparency, collaboration, and synchronisation, Scrum of Scrums, Product Owners to define the overall vision. Large Solutions - ar...
Post a Comment
Read more

4 T's - Technology, Time, Teamwork, Transparency

 1) Technology: Software development technologies are the tools and methods that developers use to design, develop, test, and deploy software applications. These include a wide range of software technologies, such as programming languages, frameworks and libraries, databases, and cloud computing platforms. 2) Time: A timebox is a fixed time period within which a deliverable must be produced in a project management context. It's a time management technique that involves dividing time into individual time periods, each with its own goal, duration, and deadline. Timeboxes are self-contained calendar events that can't be extended once they've started. The fundamental principle of timeboxing is that time in timeboxes can't shift, and once the time runs out, work must stop, even if the task isn't finished.  3) Teamwork: Teamwork in project management is a measure of how well a project's team works together to achieve a goal. It involves collaboration, communication, a...
Post a Comment
Read more