Skip to main content

What is the velocity of an Agile scrum methodology?


Let's discuss some of the important measurements in Agile, and that is the Velocity of the Scrum team work.
Based on Wikipedia definition Velocity is " ...the rate of change of its position with respect to a frame of reference and is a function of time...", which when transferred to the scrum world can be summarized as: The amount of work that the scrum team completed in a single measure of time - in a sprint.

How we Calculate Velocity?
Velocity is actually a very simple to calculate, it is done but totaling the number of story points of fully completed user stories from the sprint backlog. So if a current sprint included 4 user stories: 2 with 8 story points each, one with 3 story points and one with 32 story points. and by the end of the sprint the 32 one was not fully done the velocity calculation will be:
8+8+3=19
Note: the 32 story points are not part of the velocity calculation as this user story was not completed.

What Velocity is used for?
The velocity is used in Agile to estimate the team work and measure its success, that usually is done in a Velocity Chart:

Such chart is used to estimate how much work (story points) are completed during each sprint, and to indicate the expectations from the scrum team.
Usually new to Agile are concern how to built this chart before the work begins and the recommendation here is to estimate for 1/3 of the maximum capacity of the team. If a developer confident that he can complete 32 story points in a sprint, for the first sprint I suggest to assign no more that 13 story points to such developer and adjust the  estimated velocity as required after real velocity is calculated.

Velocity Chart also feeding data into iteration Burndown Charts which is another important metric for a scrum team.

Labels:

Comments

Post a Comment

Popular posts from this blog

What is Quality Assurance?

What is Quality Assurance (QA) in the software development world? This one will be the most popular question,with the widest variety of answers, which by its own gives me a good reason to answer it. So, I will start with dictionary(Wikipedia) definition: Quality assurance, or QA (in use from 1973) for short, is the systematic monitoring and evaluation of the various aspects of a project, service or facility to maximize the probability that minimum standards of quality are being attained by the production process. QA cannot absolutely guarantee the production of quality products . By large this is a nice definition, though it has two issues that need to be discussed further more: 1.minimum standard of quality. 2.quality of a product. But before we go there let me say something about "assurance"
4 comments
Read more...

Proper QA estimation in Agile project

  Today, I want to chat about a common issue in Agile development – story point estimation. You see, it's easy to get caught up in estimating how long a feature will take to develop and forget about the crucial Quality Assurance (QA) effort.  It happens to often: your team is in the middle of sprint planning. New user stories are being discussed, and estimations are given, but there's a catch. You've estimated the development time perfectly, but you've barely even glanced at how much effort QA will take. Why? Agile talks about Development Team and you mistakenly thought that it is all about DEVELOPMENT. Sound familiar? Trust me; it's a more common scenario than you might think. So, what's the big deal? Well, when you leave QA effort out of the equation, several not-so-great things can happen: Vilocity can suffer: You might think you can squeeze more into a sprint than is humanly possible, setting your team up for disappointment and overcommitment. Quality can de...
Post a Comment
Read more...