(mis)understanding flow with metrics - johan karlsson
TRANSCRIPT
(Mis)Understanding ‘Flow’ with Metrics
Johan KarlssonBrewing Agile 2014
Structure Fascist
Deep Experience from the Trenches
Done some coding
Creative Genius
Source: http://commons.wikimedia.org/wiki/File:Mercator_projection_SW.jpg
Why do we need to understand flow with metrics?
94 %
Percentage of problems caused by system vs people
Image source: http://commons.wikimedia.org/wiki/File:Challenge_vs_skill.svg
A BDesired
state
Build
Learn Measure
Time
Per
form
ance
“There is nothing new to be discovered in physics now. All that remains is more and more precise measurement.”Lord Kelvin
1900
“Hmm….”Einstein, publisher of a paper on relativity theory a few years later.
Are we experiencing a paradigm shift in how metrics are being used?
Current paradigm:Working software is the primary measure of progress*
Next paradigm:Do not stay dogmatic about which metrics that are being used
* Principles behind the Agile Manifesto: http://agilemanifesto.org/principles.html
Current paradigm:“In God we trust, all other bring data”*
*Famous quote, often attributed to Deming
Next paradigm:In people we trust, only bring data you care about for a very good reason
Current paradigm:Performance is reviewed with metrics
Next paradigm:The Death of Reporting: Use scientific methods to discover and teach to stakeholders what actually affects outcome
Tip: Arne Roock - Learning from Fake Charts: http://vimeo.com/80365303
Manual Creation and Maintenance
Automatic Creation and Maintenance
High Cost Low Cost
Whiteboards, stickers etcData warehousing, traditional reporting
solutions
Powerful data automation and visualization solutions
Improved Agile/Lean Practices
Easier and Cheaper Technology
The usual suspects in current paradigm when asking about metrics (outside of code stuff)
Time Time
Wor
k re
mai
ning
# N
ew B
ugs
Lead time
Work-in-process Development-in-process
Arrival rate
Departure ra
te
0 10 20 30 40 Time in days
Num
ber
of it
ems
or e
.g.
stor
y po
ints
A BDesired
state
Flow in theory
Flow in reality
a
A
B
d+cd
d
f
Desired state
?
A good method to understand and uncover complex flows is a competitive
advantage
Actors
Structures Processes
● Stakeholders (customers, investors)
● Product Owner
● Team
● Backlogs● Sprints● Hierarchy● Budgets
● Ceremonies:o Stand-ups, planning,
reviews etc● HR, IT, budgeting processes
Revenue / Delivered story points
Time
Cost ofdelay
_____________________________________________________________________________________________________________________
$$$
$
Time
S
XXL
Size
Grooming process + WSJF
Yesterday’s Weather
Outcome
Take an Economic Perspective
Measure validity of advice(example DEEP)
Ave
rage
Siz
e
No Prio
Low Prio
Medium Prio
High Prio
Do not stay dogmatic
Truly informed decision making
The death of Reporting
Organizations that discover their actual flow will be kings and queens in the next paradigm.
Inspiration in addition to our Customers:
Donald G. Reinertsen
The Principles of Product Development Flow
2012
Douglas W. Hubbard
How to Measure Anything: Finding the Value of Intangibles in Business
2014
Thomas S. Kuhn
The Structure Of Scientific Revolutions
1970
Michael Lewis
Moneyball
2011