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

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

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

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

5. 100
Remaining Task Hours
What 65
75
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
Remaining Task Hours
What 65
75
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. 65 hours could equal...
What
Story # Status Total Hours Hours Remaining = 65
10 Not Done 20 13
11 Not Done 20 13
12 Not Done 20 13
is wrong with this? 13 Not Done 20 13
14 Not Done 20 13
1. Unclear Information OR
Story # Status Total Hours Hours Remaining = 65
10 Done 15 0
11 Done 10 0
12 Done 10 0
13 Not Done 35 35
14 Not Done 30 30
And quite a few other scenarios....

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

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

10. What
is wrong with this?
3. Inaccuracies

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

12. What
is wrong with this?
4. Wasteful

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

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

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

16. What
do we recommend instead?

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

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

19. Always measure what the customer wants
What
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 Show Set Email Save Edit Delete
Location Location Preferences Search Search Search

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

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

25. What does this report tell you?
How much is done
How
What’s done
What’s not done
100%
Measure Story Completion 75%
50%
25%
0%
Set Show Set Email Save Edit Delete
Location Location Preferences Search Search 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?
Changes in scope.
How
Burnup to a fixed date

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

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

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

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