Embed Size (px)
Citation preview
Work->Data->Insight->ActionCaseStudiesofContinuousImprovementthroughMetrics
JimDamatoPMI-ACP,SA,CSP,CSM,PMP,ITILSolutionsArchitect,[email protected]
10/18/2016
AgileProfessionalsMeetup
RallySoftwareisnowpartofCATechnologies
2 ©2016CA.ALLRIGHTSRESERVED.
How long will it take a ScrumMaster to
screw in a lightbulb?
3 ©2016CA.ALLRIGHTSRESERVED.
Two Points!
4 ©2016CA.ALLRIGHTSRESERVED.
5 ©2016CA.ALLRIGHTSRESERVED.
6 ©2016CA.ALLRIGHTSRESERVED.
Me (without gray hair)
7 ©2016CA.ALLRIGHTSRESERVED.
You?
8 ©2016CA.ALLRIGHTSRESERVED.
Why a presentation on metrics?
9 ©2016CA.ALLRIGHTSRESERVED.
Why a presentation on metrics?
Too many organizations don’t measure anything
10 ©2016CA.ALLRIGHTSRESERVED.
Why do we measure?
11 ©2016CA.ALLRIGHTSRESERVED.
Why do we measure?
If you can’t measure it, you can’t manage it
12 ©2016CA.ALLRIGHTSRESERVED.
What are metrics for?
13 ©2016CA.ALLRIGHTSRESERVED.
What are metrics for?
Finding your problems(aka Continuous Improvement)
14 ©2016CA.ALLRIGHTSRESERVED.
15 ©2016CA.ALLRIGHTSRESERVED.
How do we use metrics?
16 ©2016CA.ALLRIGHTSRESERVED.
How do we use metrics?
Work -> Data -> Insight -> Action
ContinuousImprovementx/t
17 ©2016CA.ALLRIGHTSRESERVED.
Virtue vs Sin
As a lever to drive someone else's behavior
For feedback to improve your own performance
18 ©2016CA.ALLRIGHTSRESERVED.
What’s the most important measurement
in Agile?
19 ©2016CA.ALLRIGHTSRESERVED.
Working software is the primary measure of progress.
What’s the most important measurement
in Agile?
20 ©2016CA.ALLRIGHTSRESERVED.
9,192,631,770
21 ©2016CA.ALLRIGHTSRESERVED.
9,192,631,770
Don’t be fooled by the fallacy of precision
22 ©2016CA.ALLRIGHTSRESERVED.
Let’s look at some practice metrics
23 ©2016CA.ALLRIGHTSRESERVED.
TotalTaskHoursToDo
TotalPointsAccepted
IdealTaskHoursBurndown
24 ©2016CA.ALLRIGHTSRESERVED.
Unfinishediterationplanning
Acceptedhalfofuserstoriesplanned
Accepteduserstorieslateiniteration
Remainingworkhaspeaked
Burndownisflatperiodinthemiddle
Consistentacceptanceoncestarted
ProblemSolved?
25 ©2016CA.ALLRIGHTSRESERVED.
Accepted
Defined In-Progress
Completed
26 ©2016CA.ALLRIGHTSRESERVED.
Lateacceptance
Incompleteacceptance
Dropinworkon7thday
LotsofWorkinProgress
Workcarriedoverfrompreviousiteration
27 ©2016CA.ALLRIGHTSRESERVED.
28 ©2016CA.ALLRIGHTSRESERVED.
Considerations– You’re an Agile
coach– Arrived today– Know no history– Have the metrics
– What do we see in the data?
– What would we recommend?
Agile
29 ©2016CA.ALLRIGHTSRESERVED.
Scenario 1• Company 1
– Large engineering program (15 Teams)– Adopted SAFe (Scaling Agile)
• Team 1 Data:– Velocity - Iteration 2.3 thru 5.3– Iteration 5.1, 5.2 & 5.3
30 ©2016CA.ALLRIGHTSRESERVED.
Scenario 1 - Team 1 - Velocity
31 ©2016CA.ALLRIGHTSRESERVED.
Scenario 1 - Team 1 - Velocity
32 ©2016CA.ALLRIGHTSRESERVED.
Scenario 1 - Team 1 - Iteration 5.1
33 ©2016CA.ALLRIGHTSRESERVED.
Scenario 1 - Team 1 - Iteration 5.2
34 ©2016CA.ALLRIGHTSRESERVED.
Scenario 1 - Team 1 - Iteration 5.3
35 ©2016CA.ALLRIGHTSRESERVED.
Scenario 1 - ObservationsTeam 1• Inconsistent Velocity•Acceptance work at iteration end•Lots of WIP•Not planning iteration well•Adding scope during iteration•Changing iteration length
36 ©2016CA.ALLRIGHTSRESERVED.
Scenario 2• Same Company 1
– Large engineering program (15 Teams)– Adopted SAFe (Scaling Agile)
• Team 2 Data:– Velocity - Iteration 2.3 thru 5.3– Iteration 5.1, 5.2 & 5.3
37 ©2016CA.ALLRIGHTSRESERVED.
Scenario 2 - Team 2 - Velocity
38 ©2016CA.ALLRIGHTSRESERVED.
Scenario 2 - Team 2 - Velocity
39 ©2016CA.ALLRIGHTSRESERVED.
Scenario 2 - Team 2 - Iteration 5.1
40 ©2016CA.ALLRIGHTSRESERVED.
Scenario 2 - Team 2 - Iteration 5.2
41 ©2016CA.ALLRIGHTSRESERVED.
Scenario 2 - Team 2 - Iteration 5.3
42 ©2016CA.ALLRIGHTSRESERVED.
Scenario 2 - ObservationsTeam 2§ Good velocity, trending upward§ Not entering defects§ Early acceptance of work§ Better control of WIP§ Good planning of iteration§ Consistent scope during iteration§ Changing iteration length
43 ©2016CA.ALLRIGHTSRESERVED.
Scenario 3• Same Company 1
– Large engineering program (15 Teams)– Adopted SAFe (Scaling Agile)
• Team 1 vs 2 Data:– Impact of changing timebox length
44 ©2016CA.ALLRIGHTSRESERVED.
When are these the same?
45 ©2016CA.ALLRIGHTSRESERVED.
/hour /hourandahalf
When are these the same?
46 ©2016CA.ALLRIGHTSRESERVED.
35 35
28
35
35
28
Team
1Team
2
47 ©2016CA.ALLRIGHTSRESERVED.
Scenario 3 - ObservationsTeam 1 vs 2§ DON’T CHANGE TIMEBOX!!!
48 ©2016CA.ALLRIGHTSRESERVED.
Scenario 4• New Company!!!
– Single Agile Team– Practicing Agile for 2 years– Dedicated ScrumMaster– 2 wk sprints; 3 mo releases
• Single Team Data:– Single Iteration
49 ©2016CA.ALLRIGHTSRESERVED.
Scenario 4 - Iteration
50 ©2016CA.ALLRIGHTSRESERVED.
Scenario 4 - ObservationsIteration- Task actuals increase- Task burndown flat- Late acceptance- Work carrying over from previous iterations- Unfinished work moved to next iteration- Iterations are consistently over committed - Iterations velocity is consistent, but obviously lower than what the
scope of the release is.
What would we recommend?
51 ©2016CA.ALLRIGHTSRESERVED.
Scenario 5 - Expert Level• New-New Company!!!
– Single Agile Team– Practicing Agile for 2 years– Dedicated ScrumMaster– 2 wk sprints; 3 mo releases
• Single Team Data:– Single Iteration– Entire Release
52 ©2016CA.ALLRIGHTSRESERVED.
Scenario 5 - Expert Level
53 ©2016CA.ALLRIGHTSRESERVED.
Scenario 5 - Performance Analytics
54 ©2016CA.ALLRIGHTSRESERVED.
Scenario 5
55 ©2016CA.ALLRIGHTSRESERVED.
Scenario 5 - Observations
What would we recommend?
?
56 ©2016CA.ALLRIGHTSRESERVED.
How do I get metrics like that?
57 ©2016CA.ALLRIGHTSRESERVED.
The first key to success?
58 ©2016CA.ALLRIGHTSRESERVED.
The first key to success?
Estimation!
59 ©2016CA.ALLRIGHTSRESERVED.
60 ©2016CA.ALLRIGHTSRESERVED.
61 ©2016CA.ALLRIGHTSRESERVED.
62 ©2016CA.ALLRIGHTSRESERVED.
63 ©2016CA.ALLRIGHTSRESERVED.
The second key to success?
64 ©2016CA.ALLRIGHTSRESERVED.
The second key to success?
Daily updates of progress
65 ©2016CA.ALLRIGHTSRESERVED.
TheEnd
66 ©2016CA.ALLRIGHTSRESERVED.
(Imoustacheyouaquestion!)
