Agile Estimation

18

Click here to load reader

description

How the Digital Catapult does Agile Estimation for its agile software development process.

Transcript of Agile Estimation

Page 1: Agile Estimation

Agile Estimation

Andrew Rusling

Agile Coach

@andrewrusling

Page 2: Agile Estimation

Contents

1. Agile Estimation

2. Story Points

3. Planning Poker

4. Fast Estimation

2

Page 3: Agile Estimation

Competencies

At the end of this session, I expect you will be able to:

• Summarise Agile Estimation

• Explain what Story Point’s are

• Explain what a Reference Story is.

• Participate in Planning Poker

• Participate in Fast Estimation

3

Page 4: Agile Estimation

An estimation exercise 4

Page 5: Agile Estimation

Agile Estimation – key points 5

Relative over Absolute

• Innate ability

• Speed

Group over individuals

• Individuals

• Learning

• Id issues early

• Consensus

• Speed

Speed over accuracy

• Just enough to

• Prioritise

• Plan

Page 6: Agile Estimation

Story Points, represent SIZE of a story 6

Effort

Complexity

Doubt

Page 7: Agile Estimation

Story Points are relative to each other 7

12

8

Page 8: Agile Estimation

Story Points the maths holds 8

1 2+=3

Page 9: Agile Estimation

Story Point Scale 9

00.5

1 2 3 5 8 13 20 …

My head tells me 12

0 0.5 1 2 3 5 8 13 20 40 100 ∞

Page 10: Agile Estimation

Story Points do not equate to time 10

1

8

Two graduates: Two seniors:5 days 5 days

Two graduates:Two seniors: 1 day 30 days

Page 11: Agile Estimation

Planning Poker

Preparation

At start of project/team select a Reference User Story, (2 Story Points).

1. Each team member holds one set of cards

2. Product Owner explains User Story

3. Team discusses

4. Each team member selects a card and places face down on table

5. Reveal together

6. Discuss outliers, searching for Effort, Complexity & Doubt

7. Repeat steps 4 to 6 until consensus is reached at step 5.

11

Page 12: Agile Estimation

Estimating eating fruit

2 Story Points

12

Page 13: Agile Estimation

Fast Estimation

Preparation

• Lay out one set of Planning Poker cards

• Print/write out all stories on cards/paper

• Lay down one or more reference user stories

1. Split up stories between team members.

2. Check for stories that make no sense, and discuss very briefly.

3. Time 60 seconds, in silence to place stories as a first est.

4. Time 60 seconds, in silence to move stories.

5. Go through all stories, checking consensus with team and quick votes.

13

Full explanation online

Page 14: Agile Estimation

Prepared, with five reference stories 14

Page 15: Agile Estimation

End of Fast Estimation 15

Page 16: Agile Estimation

Estimating Cooking Meals

• Eggs Benedict

• Tin Baked Beans

• Fruit Salad

• B.L.T.

• Crispy skinned Salmon

• Poached Eggs

• Soufflé

• Cheese Burger

• 64 Cup Cakes

• Pineapple upside down cake

• Burrito’s

• Mashed Potato

16

• Garden Salad

• À la carte, 3 courses for two people

• Cheese Cake

• 12 Fancy cup cakes

• Duck Ala orange

• Caesar Salad

• À la carte, 3 courses for ten people

• Lasagne

• Beef Korma

• Banoffee Pie

• Fish & Chips

Page 17: Agile Estimation

Competencies

I hope you will now be able to:

• Summarise Agile Estimation

• Explain what Story Point’s are

• Explain what a Reference Story is.

• Participate in Planning Poker

• Participate in Fast Estimation

17

Page 18: Agile Estimation

Additional Information

• Story Points are only one third of the reason for estimating

• Story Points do not equate to time

• Top Tips for Planning Poker

• ThoughtWorks How do you estimate on an agile project?

18