Upload
yuriy-chulovskyy
View
150
Download
3
Tags:
Embed Size (px)
DESCRIPTION
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.
Citation preview
Visualization of your project state
Audience: leads, developers
Yuriy Chulovskyy [email protected] friend7_chat
History of the projectWhat pushed us to measure and visualize?Our achievements and failuresQ&A (any time)
- 6 years- 20 – 40 team members in UA- 5 sub teams- 20+ applications- work for big customer
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
Let’s measure and visualize it!
What do we have?
Budget metrics:- $ planned- $ earned- GM
What do we have?
2009, q1 2009, q2 2009, q3 2009, q4 2010, q1 2010, q2 2010, q3 2010, q4 2011, q1 2011, q2 2011, q30%
2%
4%
6%
8%
10%
12%
14%
Turnover rate, quarterly
Turnover rate
Aug-10 Jul-11 Apr-122
2.5
3
3.5
4
4.5
3.21
4.15Team Satisfaction
Team Satisfaction
What do we have?Schedule: amount of unfinished tasks by team\project\QA\developer\severity
Daily Scrum meetings
Workload
Velocity?
Keep them under control!
Estimate quality
Client issues
Time by activity
Time by activity
Time to market
< 1 day 1..7 days 7..30 days > 30 days0%
10%
20%
30%
40%
50%
60%
70%
Ideal data
Time to market
< 1 day 1..7 days 7..30 days > 30 days0%
5%
10%
15%
20%
25%
30%
35%
40%
Real Data
NovDec
What else could we use?Burndown
What else could we use?
Merge results