What’s my team velocity?
I often get asked how an existing team would go about determining their Velocity (the average amount of work a team can complete in a set period of time), so I thought I'd write a post about how we've...
View ArticleVelocity can be used to measure the output of any team…
Velocity is a measure of how much work a team can complete in a set period of time. It is measured in Story Points and although it was originally created for use in Software Development scenarios, it...
View ArticleSoftware Estimation – the more precise you are, the less accurate you will be!
We often confuse 'accurate' (mean difference) with 'precise (variance)'. It would be accurate to say that I was less than six foot tall, it would be precise to say that I was... Continue reading →
View ArticleUsing Velocity to measure the Productivity of an Agile Development Team
Although you can not use Velocity to measure the productivity of one team compared to another, you can use velocity to help track the relative productivity of the same team from one sprint to another...
View ArticleValue Points – Estimating the relative value of a User Story
Value Points can be used to measure the relative value of stories using a Fibonnaci Sequence. Although not appropriate or particularly necessary in all cases e.g. primarily when you have an...
View ArticleAgile Estimation and the Cone of Uncertainty
The Cone of Uncertainty is a Project Management term used to describe the level of uncertainty existing at different stages of a project. In short, we become more certain of our estimates as we learn...
View ArticleSprint Planning: Hours or Story Points (?) – that is the question!
There is a lot of debate about whether to estimate sprint requirements in hours or to leave them in Story Points. Personally, I see pros and cons of both approaches but would use Story Points over...
View Article
