The document discusses the problems with using rollups to track progress on multi-team projects. Rollups hide valuable information about individual team and program progress. They can inaccurately forecast completion dates and set incorrect expectations. The document recommends tracking each team's progress separately without masking data and correlating program objectives with project progress to provide better visibility.

1. How do you get accurate
visibility
on a
multi-team project?

2. Success of an Agile project depends on the

3. Success of an Agile project depends on the
Cooperation and Coordination
of multiple teams

4. As such, visibility of the progress
of each team and the program as a whole

5. As such, visibility of the progress
of each team and the program as a whole
is critical

6. Rollups are not the answer

7. Rollups are not the answer
Why?

8. Rollups hide valuable information
The problem with
about individual team and program progress
Rollups
#1

9. They inaccurately forecast
The problem with when the program may be complete
Rollups
#2

10. They set incorrect expectations
The problem with
Rollups
#3

11. For example...

12. The problem with Team Chicago
Rollups
Example
Team Bangalore

13. The problem with Team Chicago
Rollups
Example Common Goal
Team Bangalore

14. The problem with Team Chicago 5 stories
Rollups
Example Common Goal 40 stories
Team Bangalore 35 stories

15. Progress of Team Chicago
The problem with
Rollups
Example

16. Progress of Team Chicago
5 stories done
The problem with
Rollups
Example

17. Progress of Team Chicago
5 stories done on Jan 1st
The problem with
Rollups
Example

18. Progress of Team Chicago
5 stories done on Jan 1st
The problem with All work complete
Rollups
Example

19. Progress of Team Bangalore
The problem with
Rollups
Example

20. Progress of Team Bangalore
10 stories done
The problem with
Rollups
Example

21. Progress of Team Bangalore
10 stories done on Jan 5th
The problem with
Rollups
Example

22. Progress of Team Bangalore
10 stories done on Jan 5th
The problem with Forecasted end date Jan 21st
Rollups
Example

23. Rollups of both teams
The problem with
Rollups
Example

24. Rollups of both teams
Incorrect forecasted end date of Jan 15th
The problem with
Rollups
Example

25. Rollups of both teams
Incorrect forecasted end date of Jan 15th
The problem with when it should be Jan 21st
Rollups
Example

26. Rollups of both teams
Incorrect forecasted end date of Jan 15th
The problem with when it should be Jan 21st
Rollups with no visibility of individual team progress
Example

27. What do we recommend for better
visibility of your program’s progress?

28. Correlate progress of program objectives with project progress
For better program
visibility

29. Correlate progress of program objectives with project progress
Track the progress of each project without masking information
For better program
visibility

30. Correlate progress of program objectives with project progress
Track the progress of each project without masking information
Get alerts when attention is needed to project schedules
For better program
visibility

31. Correlate progress of program objectives with project progress
Track the progress of each project without masking information
Get alerts when attention is needed to project schedules
For better program
Forecast the effects of scope changes on project timelines
visibility

32. What helps you get
visibility of your program?

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