Velocity is the total amount of effort points completed after an iteration. The Velocity Calculator should use at least
an average Velocity (6 iterations is a good start).
For more information on Velocity, visit Agile Alliance
Total Team Members represent the development team or team doing the work. For example, in software development, it could
include the developers, QA personnel, business analysts, and testing engineers. If those individuals affect the effort of
a task/User Story/Product Backlog Item, you should count them.
Sprint Length represents the length of your iteration. To make things simple, we used weeks. If your iteration is over 4
weeks, you should ask yourself if you working toward becoming agile.
Total Days Out represents the time your team is out of the office or not working on the project. This is important and
usually not represented in "estimates" for sprint work. One day out for one person in a 2-Week Sprint is 10% of his or
her time gone.
The Average Injection count is used to create a buffer for your team of the known unknowns (e.g., bugs from new work)
and unknown unknowns (e.g., environment issues or IT issues) that come up where the team will be pulled off sprint work.
This allows the team to set the limit of items "injected" that can't be ignored before pulling items out of a sprint. In
a perfect world, you would set the work items on the first day of the sprint during planning, but in reality, that's not
always done...businesses can't rely on perfect world.
The Average Injection Effort is a great way to add an effort to the unknowns. If you track injections, have the team put
an effort on that injection and you can start to help "estimate" the unknown. If you average 8 injections and you put an
effort of 2 on those before the sprint, you are allowing 16 points of injections before you have to start pulling items
out of a sprint. If you don't believe in injections and your business doesn't get involved, then leave those two items
blank...an congrats on being extremely agile!
The Additional Hours Subtracted can be used for items you know are coming up in the sprint. For example, a two-hour
company meeting on a Wednesday and a mandatory one-hour training video on Friday. For a team of 5, that would be 15
Additional Hours. REMEMBER: Sustainability in agile is important. Teams shouldn't be punished for external factors. They
shouldn't have to make up that work and the Velocity shouldn't be affected by these factors as well.
Rollover Points are items that were committed in the previous sprint that either weren't started or completed, so you roll
them over to the next sprint.
The Old Team Count is what your team count was for the above Current Velocity.
The New Team Count is what you are planning for in the next sprint. It will calculate what the velocity was for the Old
Team and convert it to the New Team.
The Old Sprint Length is the length of the sprint you used for the Current Velocity.
The New Sprint Length is the length of sprint you want your new Velocity for.