‘Spikes’ are time boxed periods of research and development used in Agile Software Development environments to research a concept and/or create a simple prototype.
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 hours where/whenever possible.
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 more about what we’re estimating.
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 omni-present Product Manager, these can be a useful way to prioritise and convey relative importance to a team. This approach becomes increasingly useful as teams scale to cover multiple projects combined with Business As Usual activities.
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 assuming the value of a point stays the same over time.
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…
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 can be used in just about every type of team scenario. Velocity can be measured assuming you have… : 1 team
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 done it in the past…