Tweet
Tweet

Slide 1

Slide 1 text

@everydaykanban | @bsktcase #agile2018 Julia Wester & Cheryl Hammond Data Driven Coaching

Slide 2

Slide 2 text

@everydaykanban | @bsktcase #agile2018 Who are we? Julia Wester Co-Founder & Principal Consultant Lagom Solutions https://lagom.solutions @everydaykanban Cheryl Hammond Hire Me! Seattle, Washington, USA https://linkedin.com/in/bsktcase @bsktcase

Slide 3

Slide 3 text

@everydaykanban | @bsktcase #agile2018

Slide 4

Slide 4 text

@everydaykanban | @bsktcase #agile2018

Slide 5

Slide 5 text

@everydaykanban | @bsktcase #agile2018 Planning Stand-Up / Scrum Retrospective Time in Process Throughput WiP Levels WiP Age Escaped Defects Time in Process Throughput Net Flow Flow Efficiency Defects per Environment and more...

Slide 6

Slide 6 text

@everydaykanban | @bsktcase #agile2018 Meaning is in the eye of the beholder Courtesy of Troy Magennis (@t_magennis) Team member 1 Team member 2 Team member 3 Team member 4 Team member 5 Team member 6 Team member 7 Team member 8 Team member 9 Team member 10 Team member 11 Unassigned Alias 1 Alias 2 “What a slacker!” “Wow, I bet they’re working on other priorities right now.” “Makes sense. That person’s code was part of a deep exploratory testing session.”

Slide 7

Slide 7 text

@everydaykanban | @bsktcase #agile2018 The two main goals of data driven coaching: help teams identify areas of improvement 1 avoid over-emphasizing a single measure of success 2

Slide 8

Slide 8 text

@everydaykanban | @bsktcase #agile2018 “Tell me how you’ll measure me and I’ll tell you how I’ll behave. If you measure me in illogical ways, do not complain about illogical behavior.” –Eli Goldratt

Slide 9

Slide 9 text

@everydaykanban | @bsktcase #agile2018 Best bets for measuring logically

Slide 10

Slide 10 text

@everydaykanban | @bsktcase #agile2018 Highlight trends, not data points to avoid distraction from insignificant variation

Slide 11

Slide 11 text

@everydaykanban | @bsktcase #agile2018 Trends show us:

Slide 12

Slide 12 text

@everydaykanban | @bsktcase #agile2018 How to put a focus on trends No Y-Axis Tiny #’s Trend Line Project Trend When applicable, connect data point with lines

Slide 13

Slide 13 text

@everydaykanban | @bsktcase #agile2018 Compare trends across teams Courtesy of Troy Magennis (@t_magennis)

Slide 14

Slide 14 text

@everydaykanban | @bsktcase #agile2018 Measure teams, not individuals if you want people to act like a team

Slide 15

Slide 15 text

@everydaykanban | @bsktcase #agile2018 What you measure tells the story of what you value...

Slide 16

Slide 16 text

@everydaykanban | @bsktcase #agile2018 “Fear invites wrong figures. Bearers of bad news fare badly. To keep his job, anyone may present to his boss only good news.” –W. Edwards Deming Quote from “New Economics” p. 94, Deming

Slide 17

Slide 17 text

@everydaykanban | @bsktcase #agile2018 Unexpected responses you are measuring safety whether you intend to or not

Slide 18

Slide 18 text

@everydaykanban | @bsktcase #agile2018 Use multiple competing metrics to create and maintain a stable system

Slide 19

Slide 19 text

@everydaykanban | @bsktcase #agile2018 The danger of over-optimizing for one thing... Measuring this, but not this.

Slide 20

Slide 20 text

@everydaykanban | @bsktcase #agile2018 Courtesy of Larry Maccherone (@LMaccherone)

Slide 21

Slide 21 text

@everydaykanban | @bsktcase #agile2018 QUALITY RESPONSIVENESS PRODUCTIVITY PREDICTABILITY How well? How fast? How much? Keeping pace? How repeatable? Competes with Competes with

Slide 22

Slide 22 text

@everydaykanban | @bsktcase #agile2018 Are certain quadrants more important for your team?

Slide 23

Slide 23 text

@everydaykanban | @bsktcase #agile2018 Define “health” for your context

Slide 24

Slide 24 text

@everydaykanban | @bsktcase #agile2018 ODIM https://medium.com/@lmaccherone/odim-12d80823222 Courtesy of Larry Maccherone (@LMaccherone)

Slide 25

Slide 25 text

@everydaykanban | @bsktcase #agile2018 Decide on outcomes THEN Determine your metrics Reduced time / cost for rework Should we increase time spent on testing? Are we finding defects early enough in process? % defects found per environment https://medium.com/@lmaccherone/odim-12d80823222 think of small, day-to-day decisions. Question if the measure really provides expected insight! Courtesy of Larry Maccherone (@LMaccherone)

Slide 26

Slide 26 text

@everydaykanban | @bsktcase #agile2018 ESCAPED DEFECTS Jan defects found in production Feb Mar Apr May Jun Jul Aug Sep 4 5 8 8 10 6 12 8 11 50%

Slide 27

Slide 27 text

@everydaykanban | @bsktcase #agile2018 Defects By Environment # OF DEFECTS KEY counts Jan Feb Mar Apr May Jun Jul Aug Sep STAGE PROD DEV INT

Slide 28

Slide 28 text

@everydaykanban | @bsktcase #agile2018 % OF DEFECTS Jan Feb Mar Apr May Jun Jul Aug Sep Defects By Environment percents KEY STAGE PROD DEV INT

Slide 29

Slide 29 text

@everydaykanban | @bsktcase #agile2018 QUALITY RESPONSIVENESS PRODUCTIVITY PREDICTABILITY How well? How fast? How much? Keeping pace? How repeatable? pick best representative metric for each quadrant

Slide 30

Slide 30 text

@everydaykanban | @bsktcase #agile2018 A helpful template to guide you... QUADRANT QUADRANT Courtesy of Troy Magennis (@t_magennis) Metric for Opposing Quadrant Metric for Current Quadrant

Slide 31

Slide 31 text

@everydaykanban | @bsktcase #agile2018 A helpful template to guide you... RESPONSIVENESS RESPONSIVENESS Courtesy of Troy Magennis (@t_magennis) Time in Process Sprint ??? (QUALITY)

Slide 32

Slide 32 text

@everydaykanban | @bsktcase #agile2018 Behavioral Polarity Worksheet Courtesy of Troy Magennis (@t_magennis) Troy Magennis Focused Objective

Slide 33

Slide 33 text

@everydaykanban | @bsktcase #agile2018 Lagom Discovery Canvas Get canvas and key at: https://lagom.solutions/resources

Slide 34

Slide 34 text

@everydaykanban | @bsktcase #agile2018 A helpful template to guide you... RESPONSIVENESS RESPONSIVENESS Courtesy of Troy Magennis (@t_magennis) Time in Process Sprint Escaped Defects (QUALITY)

Slide 35

Slide 35 text

@everydaykanban | @bsktcase #agile2018 Give a cheat sheet! ● What is the chart ● Intended behavior ● How to game it ● When overdriven, what moves? http://bit.ly/SimResources Courtesy of Troy Magennis (@t_magennis)

Slide 36

Slide 36 text

@everydaykanban | @bsktcase #agile2018 Sometimes it’s ok to sacrifice a bit in one area to bring the whole into harmony

Slide 37

Slide 37 text

@everydaykanban | @bsktcase #agile2018 Compare only in context to ensure you highlight meaningful differences

Slide 38

Slide 38 text

@everydaykanban | @bsktcase #agile2018 Bad Comparisons lead to Bad Insights which lead to Bad Decisions

Slide 39

Slide 39 text

@everydaykanban | @bsktcase #agile2018 Show me when to worry don’t make me guess or waste my time off

Slide 40

Slide 40 text

@everydaykanban | @bsktcase #agile2018 “First, do no harm.” “If anyone adjusts a stable process, the output that follows will be worse than if (s)he had left the process alone.” –W. Edward Deming

Slide 41

Slide 41 text

@everydaykanban | @bsktcase #agile2018 Not all variation is cause for alarm OLDEST NEWEST Wk 1 Wk 2 Wk 3 Wk 4 Wk 5 Wk 6 Wk 7 Wk 8 Courtesy of Cat Swetel (@catswetel) WiP Aging

Slide 42

Slide 42 text

@everydaykanban | @bsktcase #agile2018 Use markers to show what’s concerning Courtesy of Cat Swetel (@catswetel)

Slide 43

Slide 43 text

@everydaykanban | @bsktcase #agile2018 Find Leading Indicators WiP Report % Defects Per Env

Slide 44

Slide 44 text

@everydaykanban | @bsktcase #agile2018 Recap: The two main goals of data driven coaching: help teams identify areas of improvement 1 avoid over-emphasizing a single measure of success 2

Slide 45

Slide 45 text

@everydaykanban | @bsktcase #agile2018 Recap: Key Tips to Remember

Slide 46

Slide 46 text

@everydaykanban | @bsktcase #agile2018 What steps will you take next?

Slide 47

Slide 47 text

@everydaykanban | @bsktcase #agile2018 Resources to keep learning Balanced Metrics Dashboard http://focusedobjective.com/team-metrics-right/ by Troy Magennis, Focused Objective Lagom Discovery Canvas https://bit.ly/2vTaCXF by Julia Wester, Lagom Solutions One Metric to Rule Them All https://bit.ly/2M3gVCE by Cheryl Hammond, Secret Garden

Slide 48

Slide 48 text

@everydaykanban | @bsktcase #agile2018

Slide 49

Slide 49 text

@everydaykanban | @bsktcase #agile2018 How You Can Contact Us Julia Wester Co-Founder & Principal Consultant Lagom Solutions https://lagom.solutions @everydaykanban Cheryl Hammond Hire Me! Seattle, Washington, USA https://linkedin.com/in/bsktcase @bsktcase

Slide 50

Slide 50 text

@everydaykanban | @bsktcase #agile2018 Appendix (previous slides)

Slide 51

Slide 51 text

@everydaykanban | @bsktcase #agile2018 Pro Tip: Pies are best for eating, less so for charting... http://www.thefunctionalart.com/2012/06/fun-note-on-pie-charts.html

Slide 52

Slide 52 text

@everydaykanban | @bsktcase #agile2018 Counterpoint! Why not both?

Slide 53

Slide 53 text

@everydaykanban | @bsktcase #agile2018 Don’t Just don’t

Slide 54

Slide 54 text

@everydaykanban | @bsktcase #agile2018 Correlation isn’t causation Does this fit in this section?

Slide 55

Slide 55 text

@everydaykanban | @bsktcase #agile2018 Avoid Confusing Activity with Progress Activity metrics ● lines of code ● # of issues closed ● # of deploys per day These aren’t “bad” metrics. We should: 1. Understand what they really show 2. Show them with competing metrics to reduce gaming J

Slide 56

Slide 56 text

@everydaykanban | @bsktcase #agile2018 Know The Expiry Dates For Your Metrics J

Slide 57

Slide 57 text

@everydaykanban | @bsktcase #agile2018 Goodhart’s Law “When a measure becomes a target, it ceases to be a good measure.”

Slide 58

Slide 58 text

@everydaykanban | @bsktcase #agile2018 Exercise: Map outcomes to metrics with ODIM 1. List one outcome you are trying to achieve. 2. Determine a decision you need to make to achieve the outcome. 3. List an insight that can help you make the decision. 4. List one or more metrics that can provide the needed insight. 5. Repeat until time runs out. 10 minutes

Slide 59

Slide 59 text

@everydaykanban | @bsktcase #agile2018