Velocity – Understanding Your Points

Taarradhin

VelocityI started this project to help me find the right data points to assist not only with better iteration planning but also to help me plan future iterations with a solid estimate of what we typically complete. I started off by looking at our Velocity, typically the number you use but not something we find as a good predictor of success. To figure out why, I separated out, by iteration, our planned points, our actual points and the average of the actuals.

As you can see by the chart to the left, that gave a pretty clear picture of what we’ve done so far this year; we average 46 actual points per iteration but average 53 planned points. That’s basically a weeks’ worth of work that we’re off by. In doing this, I was curious to see how many points are actually being completed in the week after the iteration…

View original post 232 more words

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s