This document discusses various metrics that can be used to improve agile team efficiency, including quality metrics like code coverage and technical debt. It also covers velocity, burn down charts, burn up charts and cumulative flow diagrams. The key takeaways are to use a combination of metrics, manage work in progress to reduce risk, track business value delivered, and make process issues visible to drive continuous improvement.

1. How to Improve
Agile Team
Efficiency
Himanshu Desai (@H_Desai)
Principal Consultant, Technical Specialist
1

2. Page
Agenda
› Measures and Metrics & their suitability
› Quality
› Velocity
› Burndown
› Burnup
› Business Value Delivered
› Cumulative Flow Diagram
› Takeaway
/ Copyright ©2015 by Readify Pty Ltd2

3. Page
Bad Metrics
/ Copyright ©2014 by Readify Pty Ltd3
› Continental Airlines example
› Reducing Fuel Consumption as metrics
› Programming Example
› When you reward programmers who write lots of
code and fix lots of bugs

4. Page
Good metrics
› Affirmandreinforceagileprinciples
› Measureoutcome,notoutput
› Followtrendsnotnumbers
› Belongtoasmallsetofmetrics/diagnostics
› "Should provide fuelformeaningful conversations"
› Diagnose&improvetheprocessesthatproducebusinessvalue
› Providefeedbackonafrequentandregularbasis
› Areeasytocollect
/ Copyright ©2015 by Readify Pty Ltd4

5. Page
Quality
/ Copyright ©2015 by Readify Pty Ltd5

6. Page
Quality
› Code Coverage
› Maintability
› Technical Debt Register
/ Copyright ©2015 by Readify Pty Ltd6

7. Page
Velocity
/ Copyright ©2015 by Readify Pty Ltd7

8. Page / Copyright ©2014 by Readify Pty Ltd8
0
5
10
15
20
25
30
35
Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6
StoryPoints
Sprints
Velocity

9. Page
Pop Quiz
› Team 1
› Velocity : 50 story points
› Team 2
› Velocity: 52 story points
/ Copyright ©2015 by Readify Pty Ltd9

10. Page
Velocity
› It is not a goal
› Rate at which team can produce working software
› Factors
› Toolset
› Team composition
/ Copyright ©2015 by Readify Pty Ltd10

11. Page / Copyright ©2014 by Readify Pty Ltd11
Goodhart's
law
“When a measure
becomes a target, it
ceases to be a good
measure.”

12. Page
Velocity – Myths
› Higher velocity is always a good thing
› Not true because….
› Techdebtisbad
› Pushingtoohardonnewproductvalueandvelocitytendstoincreasetechdebt
› Key Point : Measure and limit tech debt accumulation
/ Copyright ©2015 by Readify Pty Ltd12

13. Page
Burndown
/ Copyright ©2015 by Readify Pty Ltd14

14. Page
Burndown
› Rate at which features are completed
› Completed at sprint and release level
› Point in time measurement of amount of work left to
be done
/ Copyright ©2015 by Readify Pty Ltd15

15. Page / Copyright ©2014 by Readify Pty Ltd16
0
20
40
60
80
100
120
140
160
180
200
1/5/2015 1/6/2015 1/7/2015 1/8/2015 1/9/2015 1/10/2015 1/11/2015 1/12/2015 1/13/2015 1/14/2015
POINTS/HOURS
TIME
Burndown
Actual Remaining Ideal

16. Page / Copyright ©2014 by Readify Pty Ltd17
0
20
40
60
80
100
120
140
160
180
200
1/5/2015 1/6/2015 1/7/2015 1/8/2015 1/9/2015 1/10/2015 1/11/2015 1/12/2015 1/13/2015 1/14/2015
POINTS/HOURS
TIME
Burndown
Actual Remaining Ideal

17. Page / Copyright ©2014 by Readify Pty Ltd18
0
20
40
60
80
100
120
140
160
180
200
1/5/2015 1/6/2015 1/7/2015 1/8/2015 1/9/2015 1/10/2015 1/11/2015 1/12/2015 1/13/2015 1/14/2015
POINTS/HOURS
TIME
Burndown
Actual Remaining Ideal

18. Page
Burnup
/ Copyright ©2015 by Readify Pty Ltd19

19. Page
Burnup
› Same as burn-down but...
› Instead of tracking how much work is left to be done,
we track how much work is completed so the curve
goes up, not down
› Provides the visibility of scope changes.
/ Copyright ©2015 by Readify Pty Ltd20

20. Page / Copyright ©2014 by Readify Pty Ltd21
0
5
10
15
20
25
StoryPoints
Time
Burnup
Actual Scope

21. 0
5
10
15
20
25
30
StoryPoints
Time
Burnup
Actual Scope

22. Page
Important points
› Effectively sized and testable stories.
› Allow finishing work to end quickly
› Focus on few stories at a time, rather than work on too
much at once
/ Copyright ©2015 by Readify Pty Ltd23

23. Page
How to achieve this?
› Get the product owner to provide INVEST stories.
› Provide more visibility to WHERE work is before its
DONE
› Manage the work in progress to drive focus
/ Copyright ©2015 by Readify Pty Ltd24

24. Page
Business Value Delivered
/ Copyright ©2015 by Readify Pty Ltd25

25. Page / Copyright ©2014 by Readify Pty Ltd26
0
20
40
60
80
100
120
140
160
180
200
Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5
Cumulative Business Value Delivered

26. Page
Business Value Delivered
› Assign business value to features.
› Best to assign at the epic level or group of user stories.
/ Copyright ©2015 by Readify Pty Ltd27

27. Page
Cumulative Flow Diagram
/ Copyright ©2015 by Readify Pty Ltd28

28. Page
Cumulative Flow Diagram
› The idea is to visualize where the features/stories are in
the workflow across time.
› Helps you to visualize work status in more depth
› Manage the work in progress to drive focus
/ Copyright ©2015 by Readify Pty Ltd29

29. Page / Copyright ©2014 by Readify Pty Ltd31
0
2
4
6
8
10
12
14
16
18
20
1 2 3 4 5 6 7 8 9 10
StoriesComplete
Time (Weeks)
Cumulative Flow Diagram
8. Done 7. Await Merge 6. Await Acc. 5. Testing
4. Code Review 3. Design Review 2. In Progress 1. To Do
WIP

30. Page
Take away
› What you don’t measure, you can not improve
› Use of burnup in conjunction with burndown.
› Spread the work evenly to reduce risk of leftovers.
› Velocity is not a goal
› Use CFD to identify bottleneck and take corrective
action
/ Copyright ©2015 by Readify Pty Ltd32

31. Page
Take away (Continued)
› Track Business Value Delivered. All features should be
quantified with business value. Aim for smaller feature
› Defects per sprint gives you an idea of how well the
sprint is going
› Don’t ignore developer satisfaction
› Pay up technical debt
› Manage code coverage
/ Copyright ©2015 by Readify Pty Ltd33

32. Page / Copyright ©2014 by Readify Pty Ltd34

33. Page
Make it all visible
/ Copyright ©2014 by Readify Pty Ltd35

34. Page
Thank you
Himanshu Desai
Himanshu.desai@readify.net
/ Copyright ©2015 by Readify Pty Ltd36