- An abstract number to measure size of a feature.
- Does not mean anything in isolation, but conveys relative size of features when compared.
- Different teams size-up the same features differently but the relative measures between features might be the same.
- Fibonacci series preferred as story points: 1, 2, 3, 5, 8, 13, 21, …
- Geometric series also preferred: 1, 2, 4, 8, 16, 32, …
Story point estimation allows us to:
- Rapidly estimate long-term product backlogs without requiring detailed specifications and complicated dependency charting
- Provide broader insight from diverse functional experts (which offers checks and balances and less point sensitivity) to ensure that estimates aren’t being padded nor under-baked
- Ensure that the entire ‘brains trust’ of the team is able to understand and assess the merits of the requirements, allowing for early detection of any potential issues as well as areas for improvement
- Leverage the knowledge gained from completing legacy work
- Actually have some fun whilst conducting a traditionally mundane and frustrating task. Planning Poker sessions are interactive, lively and much faster than traditional estimation marathons
- Sound pretty snazzy as talking about your ‘team velocity’ is way more exciting than mumbling something about your ‘team rate of progress’ – ok maybe leave that one out…
No comments:
Post a Comment