1 / 20

# Practical Story Sizing - PowerPoint PPT Presentation

Practical Story Sizing. Brett Maytom Senior Consultant, Readify Vic .NET – 13 Aug 2011. Talk Backlog. What is size Relative Size Sizing Scales Velocity Story Size versus Task Sizing Running Sizing Meetings Questions. What is size?. Unit of measure for work. Why Relative Sizing.

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.

## PowerPoint Slideshow about ' Practical Story Sizing' - drake

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

### Practical Story Sizing

Brett Maytom

Vic .NET – 13 Aug 2011

• What is size

• Relative Size

• Sizing Scales

• Velocity

• Story Size versus Task Sizing

• Running Sizing Meetings

• Questions

• Unit of measure for work

• Your Time IS NOT My Time

• indicate time

• Indicate skill

• include risk

• change over time

• Increase\decrease with proficiency

Four Times

Equal

Double

Half

Three Times

• Fibonacci

1 2 3 5 8 13 21 34

• Modified Fibonacci

1 2 3 5 8 13 20 50 100

• Binary

1 2 4 8 16 32 64 128

• T-Shirt

• 0 (Zero)

“Too small and not worth sizing”

• ?

“I have no idea what you are talking about”

• ∞ (Infinity)

“This is way too big”

• Rate of work of team“Team can complete X story points per sprint”

• Not individual

• Full team including BA, QA, Dev., Test, Architect, Scrum Master

• Improves with time

• Uses a relative sizing scale

• Not done at iteration planning

• Used for Release Planning

• Tasks defined in sprint planning

• Sized in hours

• Updated daily with remaining hours

• Used for sprint burndown

• Cross-check against Story Size using current velocity

• Consistent story size critical

• Large scope differences

• Clear benchmarks

• Central team

• Product owner presents a story

• Team clarify by asking questions

• “1 … 2 … 3 … show”

• Smallest and largest values explain

• Repeat until consensus reached

• Totally new technology

• Never done before

• Have no idea how to size work

• Time-boxed to a few days

A story sized in the first sprint should have the same size in later sprints

• Use relative sizes for stories

• Do not factor in effort, risk and time

• Build a list of benchmark stories

• Continually inspect that “time” is not introduced story

• Differentiate between Task and Story sizes

• Your Time IS NOT My Time

Brett Maytom

[email protected]@brettmaytom

http://brett.maytom.net