Discovering story points

@nadiazemskova

Estimates take time…and they are never precise

Why estimate?

First there were hours

Hours are dependent on individual

Hours are dependent on specialty

Hours are translated into duration

Brook’s law

Wishful thinking

People are bad at estimating time

People are good at comparison

53 2 1Compare these buildings

User story1 2

Story pointEffort Complexity Uncertainty

Planning poker

Velocity2520151050 1 2 3 4 5 6 7 8

Time-based planning Will have3 x 15 = 45 points3 x 20 = 60 points Might have Won’t have

Scope based planning200 Finish here160 with our best velocity1208040 0 0 1 2 3 4 5 6 7 8

1. How many hours are in a story point?

It’s a distribution

2. How to estimate cost?

6 .. 8 x = .. It’s a range

3. Whose points are bigger

Only for the same team

Beware of inflation

Establish common baseline

4. How to calibrate team changes

Change of velocity302010 Team member added0 1 2 3 4 5 6 7 8 9

5. How to manage the inflow

Burnup chart16012080 Done Scope40 0 0 1 2 3 4 5 6 7 8

6. How do you get started?

This is a “2”

7. Why are we back to hours?

These areare These different kind of estimates different units

8. What do you burn during sprint

Hours Task count Points

9. What if you don’t have a team?

… plan an imaginary sprint

10. What if you have different skills?

… velocity will help

… or different teams

Estimate effort, derive duration

nadezhda.zemskova@gmail.comnadezhda.zemskova@nadiazemskovahttp://ua.linkedin.com/in/nadiazemskova

Discovering story points

by Nadia Zemskova on Sep 24, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

1 Embed 257

Statistics

Discovering story points — Presentation Transcript