You don't know who is the best performer and who slows down development? You don't understand where you waste your time? Your developers doesn't like to spend time on bug fixing? We cannot improve items that we cannot measure! Measure everything and make it visible! See whether your changes improve something.

1. Visualization of your project state
Audience: leads, developers
Yuriy Chulovskyy
yuriy.chulovskyy@gmail.com
friend7_chat

2. History of the project
What pushed us to measure and visualize?
Our achievements and failures
Q&A (any time)

3. - 6 years
- 20 – 40 team
members in UA
- 5 sub teams
- 20+ applications
- work for big
customer

4. Problems
The same as for many projects:
- We spent too much time on bug fixing
- Customer often changes requirements when
everything is implemented
- Customer cannot see what is going on and
when a feature is implemented
- We don’t know performance of a developer

5. Let’s measure and visualize it!

6. What do we have?
Budget metrics:
- $ planned
- $ earned
- GM

7. What do we have?
Team Satisfaction
4.5
4.15
4
3.5 3.21
3 Team Satisfaction
2.5
2
Aug-10 Jul-11
Turnover rate, quarterly
14%
12%
10%
8%
6% Turnover rate
4%
2%
0%
2009, q1 2009, q2 2009, q3 2009, q4 2010, q1 2010, q2 2010, q3 2010, q4 2011, q1 2011, q2 2011, q3

8. What do we have?
Schedule: amount of unfinished tasks by
teamprojectQAdeveloperseverity

13. Daily Scrum meetings

14. Workload

15. Velocity?

16. Keep them under control!

17. Estimate quality

18. Client issues

19. Time by activity

20. Time by activity

21. Time to market
Ideal data
70%
60%
50%
40%
30%
20%
10%
0%
< 1 day 1..7 days 7..30 days > 30 days

22. Time to market
Real Data
40%
35%
30%
25%
20% Nov
15% Dec
10%
5%
0%
< 1 day 1..7 days 7..30 days > 30 days

23. What else could we use?
Burndown

24. What else could we use?

25. Merge results