EECS 394 Software Project Management Chris Riesbeck Tuesday, April - - PowerPoint PPT Presentation

eecs 394 software project management
SMART_READER_LITE
LIVE PREVIEW

EECS 394 Software Project Management Chris Riesbeck Tuesday, April - - PowerPoint PPT Presentation

EECS 394 Software Project Management Chris Riesbeck Tuesday, April 12, 2011 Tracking Progress Burndown Charts Burnup Charts Velocity Chapter 8, Agile Samurai 2 Tuesday, April 12, 2011 Burndown


slide-1
SLIDE 1

Chris Riesbeck

EECS 394 Software Project Management

Tuesday, April 12, 2011

slide-2
SLIDE 2

Tracking Progress

2

Burndown Charts Burnup Charts Velocity

Chapter 8, Agile Samurai

Tuesday, April 12, 2011

slide-3
SLIDE 3

3

Burndown Charts

http://rapidapplicationdevelopment.blogspot.com/ 2008/10/forget-burndown-use-burnup-charts.html

A simple graph of points left in release backlog

Tuesday, April 12, 2011

slide-4
SLIDE 4

3

Burndown Charts

http://rapidapplicationdevelopment.blogspot.com/ 2008/10/forget-burndown-use-burnup-charts.html

velocity A simple graph of points left in release backlog

Tuesday, April 12, 2011

slide-5
SLIDE 5

3

Burndown Charts

http://rapidapplicationdevelopment.blogspot.com/ 2008/10/forget-burndown-use-burnup-charts.html

velocity A simple graph of points left in release backlog

Tuesday, April 12, 2011

slide-6
SLIDE 6

4

Velocity

number of story points per iteration an empirical value calculated for each team for each project velocity determines the number of points you can commit to for an iteration N usually stabilizes after the first few iterations

Tuesday, April 12, 2011

slide-7
SLIDE 7

5

Burndown Charts

http://rapidapplicationdevelopment.blogspot.com/ 2008/10/forget-burndown-use-burnup-charts.html

Tuesday, April 12, 2011

slide-8
SLIDE 8

5

Burndown Charts

why did velocity decrease here? http://rapidapplicationdevelopment.blogspot.com/ 2008/10/forget-burndown-use-burnup-charts.html

Tuesday, April 12, 2011

slide-9
SLIDE 9

6

Burnup Charts

http://rapidapplicationdevelopment.blogspot.com/ 2008/10/forget-burndown-use-burnup-charts.html

graph total points in backlog and points completed

Tuesday, April 12, 2011

slide-10
SLIDE 10

6

Burnup Charts

velocity was constant! http://rapidapplicationdevelopment.blogspot.com/ 2008/10/forget-burndown-use-burnup-charts.html

graph total points in backlog and points completed

Tuesday, April 12, 2011

slide-11
SLIDE 11

6

Burnup Charts

velocity was constant! stories were added http://rapidapplicationdevelopment.blogspot.com/ 2008/10/forget-burndown-use-burnup-charts.html

graph total points in backlog and points completed

Tuesday, April 12, 2011

slide-12
SLIDE 12

7

http://www.total-quality-management-software.com/gantt-chart-examples.asp

Gantt Charts

Tuesday, April 12, 2011

slide-13
SLIDE 13

8

Apr 1 Apr 8 Apr 15 Apr 22

Iteration 1 Iteration 2 Iteration 3 Iteration 4

Release Gantt Math

Tuesday, April 12, 2011

slide-14
SLIDE 14

8

Apr 1 Apr 8 Apr 15 Apr 22

Iteration 1 Iteration 2 Iteration 3 Iteration 4

Apr 4 Iteration 1 slips 1 day (timeboxes not fixed)

Release Gantt Math

Tuesday, April 12, 2011

slide-15
SLIDE 15

8

Apr 1 Apr 8 Apr 15 Apr 22

Iteration 1 Iteration 2 Iteration 3 Iteration 4

Apr 4 Iteration 1 slips 1 day (timeboxes not fixed)

Release

What does this predict for the new end date?

Gantt Math

Tuesday, April 12, 2011

slide-16
SLIDE 16

8

Apr 1 Apr 8 Apr 15 Apr 22

Iteration 1 Iteration 2 Iteration 3 Iteration 4

Apr 4 Iteration 1 slips 1 day (timeboxes not fixed) Apr 25

Release

What does this predict for the new end date?

Gantt Math

Tuesday, April 12, 2011

slide-17
SLIDE 17

9

Apr 1 Apr 8 Apr 15 Apr 22

Iteration 1 Iteration 2 Iteration 3 Iteration 4

Release Backlog Math

Tuesday, April 12, 2011

slide-18
SLIDE 18

9

Apr 1 Apr 8 Apr 15 Apr 22

Iteration 1 Iteration 2 Iteration 3 Iteration 4

5 5 5 5 20 points in release plan

Release

Expected velocity = 5

Backlog Math

Tuesday, April 12, 2011

slide-19
SLIDE 19

9

Apr 1 Apr 8 Apr 15 Apr 22

Iteration 1 Iteration 2 Iteration 3 Iteration 4

5 5 5 5 4 20 points in release plan

Release

Expected velocity = 5 Actual velocity for iteration 1 = 4

Backlog Math

Tuesday, April 12, 2011

slide-20
SLIDE 20

9

Apr 1 Apr 8 Apr 15 Apr 22

Iteration 1 Iteration 2 Iteration 3 Iteration 4

5 5 5 5 4 20 points in release plan

Release

Expected velocity = 5 Actual velocity for iteration 1 = 4 What does this predict for the new end date?

Backlog Math

Tuesday, April 12, 2011

slide-21
SLIDE 21

9

Apr 1 Apr 8 Apr 15 Apr 22

Iteration 1 Iteration 2 Iteration 3 Iteration 4

5 5 5 5 4 20 points in release plan

Release

Expected velocity = 5 Actual velocity for iteration 1 = 4 4 4 4 4 Apr 29! What does this predict for the new end date?

Backlog Math

Tuesday, April 12, 2011

slide-22
SLIDE 22

Slicing into Very Small Releases

10

http://toni.org/2010/05/19/in-praise-of-continuous- deployment-the-wordpress-com-story/ http://agile.dzone.com/news/holy-trinity-continuous page 178 Agile Samurai

http://johannesbrodwall.com/2010/10/18/ development-battle-plan/

http://blogs.agilefaqs.com/2009/05/03/thin-slice/

The key to daily delivery of user stories (client value)

Tuesday, April 12, 2011