Agile Planning, Estimation And Tracking

building software to help our clients growSINCE 1985

www.tallan.com

Agile Project Estimating, Planning and Tracking

Andrew Nichols, Certified Scrum Master

7/3/2009Tallan, Inc. Proprietary and Confidential. Copyright 2009

[email protected]


How to plan an Agile project

Develop product backlog

Estimating backlog

Calculating project duration and budget

Prioritize backlog

Release planning

How to track an Agile project

Agenda

7/3/2009Tallan, Inc. Proprietary and Confidential. Copyright 2009 2

List for all features desired in system

User Stories

Use Cases

Just list the features any way you want

This is open to change

Not everything will be implemented

Ideas not on the list will be discovered along the way

Develop Product Backlog

Product Backlog


# Description

1 Story A

2 Story B

3 Story C

4 Story D

5 Story E

6 Story F

7 Story G

8 Story H

9 Story I

10 Story J

11 Story K

Develop Product Backlog

Product Backlog Exercise



Petbook will be a website which connects pet owners together so that they can network and exchange information about their pets and find other pet owners like them.

Petbook will be a brand new website and should NOT be a replica of Facebook.

It will be developed from scratch and will not use any existing social networking platform.

Petbook

Social network for pet owners


Estimating Backlog

How long will this

take?

Productivity: Time vs. Quality


http://www.joelonsoftware.com/articles/HighNotes.html

Stanley Eisenstat at Yale. CS 323 Programming Assignments Show

10:1 difference in productivity

Measurement of duration

Should be relative

Meaningless without velocity

Difficult to get management away from calendar days

Measurement of effort not duration

Relative not absolute

Meaningless without velocity

Difficult for management to understand

Ideal Days Story Points

Estimating Backlog


0

2

4

6

8

10

12

14

16

18

Exponential Series


0 1 2 3 5 813

20

40

100

Modified Fibonacci Series

Estimating Backlog

Story Points


Expert Judgment

Analogy

Disaggregation

Planning Poker

Estimation

Methods of Estimation


1. Everyone has set of cards with points on them

2. Discuss the feature to be estimated

3. Everyone shows card with estimate simultaneously

4. If all cards same then you are done

5. If there is disparity then go to 2

Estimation

Planning Poker

Planning Poker Exercise



# Description Effort (Story Points)

1 Story A 2

2 Story B 8

3 Story C 8

4 Story D 1

5 Story E 13

6 Story F 5

7 Story G 2

8 Story H 5

9 Story I 1

10 Story J 3

11 Story K 5

Product Backlog


Points completed per iteration

Best determined imperially

Worst case make an assumption

Iteration Planning

Velocity


P = Points per story

V = Velocity

Duration and Budget

Estimated Duration

V

PD


R = Run rate per iteration

Duration and Budget

Estimated Budget

DRB

Calculate Duration and Budget Exercise



Financial Prioritization

Desirability Prioritization

Not used for Mandatory features

Used to trade off between optional features

Prioritize Backlog

Methods of Prioritization


Use numbers to assign priority

Higher priority = higher number

No 2 stories have same priority

Prioritization Tips

Prioritization Exercise



# Description Effort (Story Points) Priority

1 Story A 2 100

2 Story B 8 101

3 Story C 8 90

4 Story D 1 95

5 Story E 13 50

6 Story F 5 35

7 Story G 2 30

8 Story H 5 25

9 Story I 1 20

10 Story J 3 15

11 Story K 5 10

Product Backlog


Plan 2-3 iterations out

Break stories up vertically if necessary

Set a commitment base goal

Set a stretch goal (base + 20%)

Release Planning

Release Planning


# Description Effort (Story

Points)

Priority Iteration

1 Story A 2 100 1

2 Story B 8 101 1

3 Story C 8 90 2

4 Story D 1 95 2

5 Story E 13 50 3

6 Story F 5 35

7 Story G 2 30

8 Story H 5 25

9 Story I 1 20 2

10 Story J 3 15

11 Story K 5 10

Product Backlog


Always meet your commitment

Always deliver a few of the stretch goals

Discuss plan with entire team

Release Planning

Tips


How to plan an Agile project

How to track an Agile project

Tracking Velocity

Projecting Duration and Budget

Agenda


Iteration and team level not developer

Completed features not specs or documents

Tracking Progress


19

21

23

25

27

29

31

33

35

1 3 5 7 9 11 13 15 17 19 21 23

Velocity

Average Velocity

Tracking Velocity


Projected Duration

Projected Budget

Duration and Budget

A

r

SpV

PDD

PSP DRBB


...)()()( 2

33

2

22

2

11 awawawAP

Buffering for Risk and Uncertainty


Estimate average case effort estimate

Estimate worst case effort estimate

(worst – average)2

Total points = Sum of average + square root of sum of squares

Buffering

Buffering for Risk and Uncertainty


# Description Average Case Worst Case (worst – average)2

1 Story A 2 3 1

2 Story B 8 13 25

3 Story C 8 20 144

4 Story D 1 2 1

5 Story E 13 40 729

6 Story F 5 8 9

7 Story G 2 8 36

8 Story H 5 8 9

9 Story I 1 2 1

10 Story J 3 5 4

11 Story K 5 8 9

53 117 968

Product Backlog


Average Case = 53

Buffer = 31

Total Points = 53 + 31 = 84

Buffering


Results in more predictable schedule up front

Identifies high risk stories

Buffering

Benefits


# of points are meaningless

# of stories are meaningless

What’s important:

Velocity vs. Total Points

Always complete some of the stretch goals

Conclusions

Agile Planning, Estimation And Tracking

Technology

Transcript of Agile Planning, Estimation And Tracking