Agile Metrics - Speaker Deck

Slide 1

Slide 1 text

Metrics That Matter Todd Kaufman Saturday, March 10, 12

Slide 2

Slide 2 text

Metrics That Matter Todd Kaufman Saturday, March 10, 12

Slide 3

Slide 3 text

How to stop abusing yourself and others with Metrics Todd Kaufman Saturday, March 10, 12

Slide 4

Slide 4 text

Metrics are ______ to a software development team? Saturday, March 10, 12

Slide 5

Slide 5 text

How does your boss, product owner, or client answer that question? Saturday, March 10, 12

Slide 6

Slide 6 text

Lights On! Saturday, March 10, 12

Slide 7

Slide 7 text

Defects are up! Saturday, March 10, 12

Slide 8

Slide 8 text

Velocity is down! Saturday, March 10, 12

Slide 9

Slide 9 text

We’re tracking a month late! Saturday, March 10, 12

Slide 10

Slide 10 text

Saturday, March 10, 12

Slide 11

Slide 11 text

An example to illustrate... Saturday, March 10, 12

Slide 12

Slide 12 text

Team is achieving 20 pts per iteration Saturday, March 10, 12

Slide 13

Slide 13 text

Team is achieving 20 pts per iteration Release is planned at 4 iterations out Saturday, March 10, 12

Slide 14

Slide 14 text

Team is achieving 20 pts per iteration Release is planned at 4 iterations out Sprint backlog is estimated at 70 pts left Saturday, March 10, 12

Slide 15

Slide 15 text

Team is achieving 20 pts per iteration Release is planned at 4 iterations out Sprint backlog is estimated at 70 pts left Team hits 17 pts next iteration Saturday, March 10, 12

Slide 16

Slide 16 text

Team is achieving 20 pts per iteration Release is planned at 4 iterations out Sprint backlog is estimated at 70 pts left Team hits 17 pts next iteration Team hits 7 pts next iteration Saturday, March 10, 12

Slide 17

Slide 17 text

Slide 18

Slide 18 text

Slide 19

Slide 19 text

Pressure Causes Fractures Saturday, March 10, 12

Slide 20

Slide 20 text

Once these cracks have developed... Saturday, March 10, 12

Slide 21

Slide 21 text

They cannot be easily mended Saturday, March 10, 12

Slide 22

Slide 22 text

Saturday, March 10, 12

Slide 23

Slide 23 text

sadometricism Saturday, March 10, 12

Slide 24

Slide 24 text

sadometricism The gratiﬁcation of oneself through metrics to the point of pain for the individual and those around them. Saturday, March 10, 12

Slide 25

Slide 25 text

Can we maintain visibility without obsession? Saturday, March 10, 12

Slide 26

Slide 26 text

Yes! If we just use some common sense Saturday, March 10, 12

Slide 27

Slide 27 text

Protip 1: Only use metrics when answering a question Saturday, March 10, 12

Slide 28

Slide 28 text

Protip 2: Understand your audience Saturday, March 10, 12

Slide 29

Slide 29 text

Protip 3: Empower your team Saturday, March 10, 12

Slide 30

Slide 30 text

Protip 4: Pick the best metric for the job Saturday, March 10, 12

Slide 31

Slide 31 text

Protip 5: Favor metrics that are difficult to game Saturday, March 10, 12

Slide 32

Slide 32 text

From Misused to Rarely Used... Saturday, March 10, 12

Slide 33

Slide 33 text

Velocity! Saturday, March 10, 12

Slide 34

Slide 34 text

How could velocity possibly be misused? Saturday, March 10, 12

Slide 35

Slide 35 text

Velocity is down! Saturday, March 10, 12

Slide 36

Slide 36 text

Velocity is up! Saturday, March 10, 12

Slide 37

Slide 37 text

Team or individual comparison Saturday, March 10, 12

Slide 38

Slide 38 text

Velocity isn’t all bad Saturday, March 10, 12

Slide 39

Slide 39 text

Story Points Remaining Saturday, March 10, 12

Slide 40

Slide 40 text

Precision implies Accuracy Saturday, March 10, 12

Slide 41

Slide 41 text

Assumes knowledge of the unknown Saturday, March 10, 12

Slide 42

Slide 42 text

Stories are like rabbits Saturday, March 10, 12

Slide 43

Slide 43 text

BTW, how did you estimate all these stories ? Saturday, March 10, 12

Slide 44

Slide 44 text

Saturday, March 10, 12

Slide 45

Slide 45 text

If you need a swag, base it off epics, features, or stories and assume change Saturday, March 10, 12

Slide 46

Slide 46 text

Favor burnups if you need graphs Saturday, March 10, 12

Slide 47

Slide 47 text

Change Introduced !20$ 0$ 20$ 40$ 60$ 80$ 100$ Itera.on$1$ Itera.on$2$ Itera.on$3$ Itera.on$4$ Itera.on$5$ Itera.on$6$ Itera.on$7$ Itera.on$8$ Itera.on$9$ Itera.on$10$ Itera.on$11$ Itera.on$12$ Itera.on$13$ Cumula.ve$ Remaining$ Saturday, March 10, 12

Slide 48

Slide 48 text

We all have deep scars from waterfall projects Saturday, March 10, 12

Slide 49

Slide 49 text

Resistance to change Saturday, March 10, 12

Slide 50

Slide 50 text

What question does this metric answer? Saturday, March 10, 12

Slide 51

Slide 51 text

Contracting on this rarely works Saturday, March 10, 12

Slide 52

Slide 52 text

Saturday, March 10, 12

Slide 53

Slide 53 text

Lines of Code Saturday, March 10, 12

Slide 54

Slide 54 text

Code Coverage Saturday, March 10, 12

Slide 55

Slide 55 text

Cyclomatic Complexity Saturday, March 10, 12

Slide 56

Slide 56 text

Cyclomatic Complexity + Code Coverage Saturday, March 10, 12

Slide 57

Slide 57 text

Broken Builds Saturday, March 10, 12

Slide 58

Slide 58 text

Defects Saturday, March 10, 12

Slide 59

Slide 59 text

Cycle Time Saturday, March 10, 12

Slide 60

Slide 60 text

cycle time > velocity when... Saturday, March 10, 12

Slide 61

Slide 61 text

Cards are all relatively equal sized Saturday, March 10, 12

Slide 62

Slide 62 text

Team is mature enough to resist commitments and estimation Saturday, March 10, 12

Slide 63

Slide 63 text

Past performance does not guarantee future results Saturday, March 10, 12

Slide 64

Slide 64 text

Team Happiness Saturday, March 10, 12

Slide 65

Slide 65 text

“Negativity kills innovation” - Venkat S. Saturday, March 10, 12

Slide 66

Slide 66 text

Difficult to quantify Saturday, March 10, 12

Slide 67

Slide 67 text

Saturday, March 10, 12

Slide 68

Slide 68 text

Business Value Earned Saturday, March 10, 12

Slide 69

Slide 69 text

Which means more to your business? $ earned story points delivered Saturday, March 10, 12

Slide 70

Slide 70 text

C*Os understand and speak this language Saturday, March 10, 12

Slide 71

Slide 71 text

Contracting by this means true alignment Saturday, March 10, 12

Slide 72

Slide 72 text

Running Tested Features Saturday, March 10, 12

Slide 73

Slide 73 text

“Nearly every metric can be perverted, since up- and down-ticks in the metric can come from good or bad causes. Teams driven by metrics often game the metrics rather than deliver useful software. Ask the team to deliver and measure Running Tested Features, week in and week out, over the course of the entire project. Keeping this single metric looking good demands that a team become both agile and productive." Saturday, March 10, 12

Slide 74

Slide 74 text

Features Used Saturday, March 10, 12

Slide 75

Slide 75 text

How much would you pay to know what features your customers used and what they didn’t? Saturday, March 10, 12

Slide 76

Slide 76 text

Validated Learning Saturday, March 10, 12

Slide 77

Slide 77 text

Validated learning is the process of demonstrating empirically that a team has discovered valuable truths about a startup’s present and future business prospects. Eric Ries - The Lean Startup Saturday, March 10, 12

Slide 78

Slide 78 text

Talk to your Customers! Saturday, March 10, 12

Slide 79

Slide 79 text

So what have we learned? Saturday, March 10, 12

Slide 80

Slide 80 text

STOP the abuse! Saturday, March 10, 12

Slide 81

Slide 81 text

Saturday, March 10, 12

Slide 82

Slide 82 text

Metrics are information radiators Saturday, March 10, 12

Slide 83

Slide 83 text

Metrics are information radiators Leverage them Saturday, March 10, 12

Slide 84

Slide 84 text

Metrics are information radiators Leverage them Only when solving a problem Saturday, March 10, 12

Slide 85

Slide 85 text

Metrics are information radiators Leverage them Only when solving a problem That is worth solving Saturday, March 10, 12

Slide 86

Slide 86 text

“Not everything that counts can be counted, and not everything that can be counted counts.” Saturday, March 10, 12