Data Driven Coaching - Agile 2018

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

@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

@everydaykanban | @bsktcase #agile2018

@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...

@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.”

@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

@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

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

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

@everydaykanban | @bsktcase #agile2018 Trends show us:

@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

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

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

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

@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

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

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

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

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

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

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

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

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

@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)

@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%

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

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

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

@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

RESPONSIVENESS RESPONSIVENESS Courtesy of Troy Magennis (@t_magennis) Time in Process Sprint ??? (QUALITY)

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

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

RESPONSIVENESS RESPONSIVENESS Courtesy of Troy Magennis (@t_magennis) Time in Process Sprint Escaped Defects (QUALITY)

@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)

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

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

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

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

@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

@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

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

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

@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

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

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

@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

@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

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

@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

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

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

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

@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

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

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

@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

Data Driven Coaching - Agile 2018

Data Driven Coaching - Agile 2018

More Decks by Julia Wester

Other Decks in Business

Featured

Transcript