Look beyond the burndown. Explore other ways to measure progress on an Agile project

1. What
is the best way to measure
progress on an Agile project?

2. 100
75
The Ubiquitous Burndown?
50
25
0
June 6
June 7
June 8
June 9
June 10
June 13
June 14
June 15
June 16
June 17

3. What
is wrong with this?
The Ubiquitous Burndown?
100
75
50
25
0
June 7
June 9
June 13
June 15
June 17

4. What
is wrong with this?
1. Unclear Information

5. 100
What
Remaining Task Hours
75
65
50
is wrong with this?
25
1. Unclear Information
0
June 6 June 7 June 8 June 9 June 10 June 13 June 14 June 15 June 16 June 17
What does this burndown tell you?

6. 100
What
Remaining Task Hours
75
65
50
is wrong with this?
25
1. Unclear Information
0
June 6 June 7 June 8 June 9 June 10 June 13 June 14 June 15 June 16 June 17
What does this burndown tell you?
Here we are on June 10th
with 65 task hours remaining.

7. What
65 hours could equal...
1. Unclear Information
Status
Total Hours
Hours Remaining = 65
10
Not Done
20
13
11
Not Done
20
13
12
Not Done
20
13
13
Not Done
20
13
14
is wrong with this?
Story #
Not Done
20
13
OR
Story #
Status
Total Hours
Hours Remaining = 65
10
11
12
13
14
Done
Done
Done
Not Done
Not Done
15
10
10
35
30
0
0
0
35
30
And quite a few other scenarios....

8. What
is wrong with this?
2. No visibility of scope

9. What
is wrong with this?
2. No visibility of scope
And scope creep

10. What
is wrong with this?
3. Inaccuracies

11. What
is wrong with this?
3. Inaccuracies
A burndown holds accurate data if:
Every team member remembers to
accurately estimate the hours remaining on
all their tasks every single day,
and enter it into the system every single day.

12. What
is wrong with this?
4. Wasteful

13. What
is wrong with this?
4. Wasteful
A
lot of effort spent making
frequent estimates and updates

14. What
is wrong with this?
4. Wasteful
For a report that has:
1. Unclear information
2. No visibility of scope
3. Inaccuracies

15. What
A lot of overhead
is wrong with this?
4. Wasteful
for little benefit

16. What
do we recommend instead?

17. What
do we recommend instead?
Always measure business value

18. What
do we recommend instead?
Always measure what the customer wants

19. What
Always measure what the customer wants
do we recommend instead?
Not hours

20. How?

21. How
Measure Story Completion

22. What does this report tell you?
How
100%
Measure Story Completion
75%
50%
25%
0%
Set
Location
Show
Set Email
Location Preferences
Save
Search
Edit
Search
Delete
Search

23. What does this report tell you?
How
How much is done
100%
Measure Story Completion
75%
50%
25%
0%
Set
Location
Show
Set Email
Location Preferences
Save
Search
Edit
Search
Delete
Search

24. What does this report tell you?
How
How much is done
What’s done
100%
Measure Story Completion
75%
50%
25%
0%
Set
Location
Show
Set Email
Location Preferences
Save
Search
Edit
Search
Delete
Search

25. What does this report tell you?
How
How much is done
What’s done
What’s not done
100%
Measure Story Completion
75%
50%
25%
0%
Set
Location
Show
Set Email
Location Preferences
Save
Search
Edit
Search
Delete
Search

26. How
Burnup to a fixed date

27. What does this report tell you?
How
Burnup to a fixed date

28. What does this report tell you?
How
Burnup to a fixed date
Changes in scope.

29. What does this report tell you?
How
Burnup to a fixed date
Changes in scope.
What’s done and how we’re progressing.

30. What does this report tell you?
How
Burnup to a fixed date
Changes in scope.
What’s done and how we’re progressing.
Story count deficit on timeline.

31. What does this report tell you?
How
Burnup to a fixed date
Changes in scope.
What’s done and how we’re progressing.
Story count deficit on timeline.
Forecast completion based on previous velocity.

32. How
do you track progress on your project?

33. Agile workers talk often and welcome change. Mingle creates a shared space to
make quick decisions and track details, even when the team can’t be together.
See how Mingle can help you effectively track the progress of your project or program