written, illustrated
and performed by
Claudio Perrone
agilesensei.com
@agilesensei
Continuous evolution
Through ultra-rapid
experimentation
This…
… Is jim
He wants to get
things done
Grow
Be part of a high-performance team
Jim would like to
change the world
But the world
does not want
to be changed
His company went through many
reorganizations, only to stay the same
Organization chart
Blame flow
Rule makers
Controllers
Enforcers
VictimsOrganization chart
God
Losers
So, Today,
this is Jim.
most of us
think about
change as
big, slow
and scary
But what if we could make it
infinitely small…
… and learn to evolve
almost as fast as a virus?
“ -- 1st PopcornFlow Principle
(aka “the virus” principle)
If change is hard,
make it continuous.
Here is a “mad” thought…
trying to rewire the human brain is
difficult, however.
A better option is to ACT ON THE system
– i.e. the environment in which decisions are made.
…But how?
ARCHITECTING
CHANGE
(with PopcornFlow)
@agilesensei
A while ago, I worked with a team who
had not deployed software in months
With the motto “Hard on systems, soft
on people”, We worked together and
evolved using the kanban method
The Kanban board captured our value stream…
… But that’s
only the
outcome of
our thinking
“ -- Claudio Perrone
It’s not what you do but rather what
you learn by doing it that matters.
You see...
Problems &
observations
Options Possible
experiments
OngoingReviewNext
Committed
the real “secret” was our rapid stream of
traceable change experiments…
the real “secret” was our rapid stream of
traceable change experiments…
Problems &
observations
Options Possible
experiments
OngoingReviewNext
Committed
PopcornFlow Claudio Perrone
PopcornFlow.com
	
  h#p://agilesensei.com/resources	
  
... A powerful learning stream that I call
“popcorn Flow”...
So, we captured our learning journey
on a parallel “PopcornFlow board”
It starts with Problems & Observations
The quality
of our code
sucks.
inertia is our enemy…
“Everybody is entitled to their own
opinion, but…
A shared opinion is a fact.
… so, I’m happy to Make progress even with
imperfect information. As a consequence…
-- 2nd PopcornFlow Principle
(aka “the kaizen urgency” principle)The quality
of our code
sucks.
The quality
of our code
sucks.
...I use shared observations to create/elicit
options (“rule of three”).
Test-driven
development
Code review
Pair
Programming
Test-driven
development
Code review
Pair
Programming
Promising options lead to a backlog of
possible experiments.
Action: Research
good books on
TDD
Action: Let’s
pair program
for 3 days
Action: Let’s pair program
Reason: Code quality sucks
Expectations:
-  Perception is that code
is better
-  We’ll like it & want to
keep doing it
Duration: 3 days
Review Date: dd/mm/yy
experiments that we Commit to pursue have an
action, reason, expectation and Review date.
Experiment: "Fix as you go": If found small bugs (less than 20mins), just
branch and fix them. Do a pull request and mark the id on the card.
Reason: too much bureaucracy for small bugs.
Expectation:
- developer happy to fix things as needed without lengthy triages.
- steadily improving quality.
- low bureaucracy, but still able to track it if things go wrong.
- at least 3 bugs fixed like this by due date.
Experiment: Pair on JIT analysisReason: We are moving towards JIT analysis to reduce sprint
planning and moving to continuous flow.Expectation:
- DoD created
- Team agrees that analysis goes smoothly- No significant bottlenecks created
Experiment: Do an Analytics meet-up to show how analytics work in <new
kanban tool>
Reason: <product owner> needs some form of predictability.
Expectation:
- Po/Team are aware of what’s possible now with the current level of
analytics
- We have better understanding of if, how, when we can improve
forecasting with minimum amount of estimation.
At Each retrospective, we ask exactly these
questions:
Action: Let’s pair program
Reason: Code quality sucks
Expectations:
-  Perception is that
code is better
-  We’ll like it & want to
keep doing it
Duration: 3 days
Review Date: dd/mm/yy
Some people fear “failure”…
Gap = Frustration
Reality
Expectation
… But we only really “fail” when we limit
our opportunities to learn
Gap = Frustration
Reality
Expectation
Learning
“ -- 3rd Popcorn Flow Principle
(aka “the skateboarder” principle)
It’s not “fail fast, fail often”…
It’s “learn fast, learn often”.
YOU SEE…
Can you REALLY
pretend that
you’ll never fall?
Right from the beginning, I knew this was
different.
... Because the team COULD easily handle
5-10 change experiments each week...
... rapidly enabling it to DELIVER
multiple times a day
…and then it spread.
Popcorn boards started to appear in other
parts of the organization.
Imagine a continuous flow of experiments to
dramatically accelerate the rate of change in
every corner of your organization...
... How far would you go?
Today, popcorn flow is entering more
organizations
It was designed to quickly introduce,
sustain & accelerate change…
… But then, I wondered: what jobs are
other people ‘hiring’ PopcornFlow for?
They “hire” a product or service
to get the job done.
Prof	
  Clayton	
  Christensen	
  
People encounter situations that
drive the need to accomplish a job.
After all…
Some teams ‘hire’ Popcornflow to better
reflect and continuously improve the way
they work.
others use it to reach product/market
fit (e.g., “improve conversion rate from
5% to 10%”)
corporate boardrooms use it for
strategic decision-making (real options)
PopcornFlow is touching lives even outside
the business world…
e.g. Families,
... Schools, autism support groups.
PopcornFlow is even part of A proposal to
foster innovation in the public sector
popcorn Flow is also getting
traction at personal level
“Every single week,
I’m 5 experiments older.
Can I evolve even faster?
Can you?
Continuous evolution
Is a way of life.
-- Claudio Perrone
Projects under active development include
a lightweight “Action Deck” to facilitate
face-to-face conversations...
(... Which I
used to help
some friends
finding a job)
...stickers, to setup a popcornflow board
like a pro in minutes...
	
  h#p://popcornflow.com/s;ckers	
  
JUST	
  
RELEASED!	
  
h#p://discuss.popcornflow.com	
  
… A discussion forum
(psst... a “secret” online platform...)
... And a book.
	
  h#p://popcornflow.com/book	
  
JOIN	
  THE	
  
EARLY	
  
NOTIFICATION	
  
LIST!	
  
Final Thoughts
“
-- Claudio Perrone
It’s not what you do but rather what
you learn by doing it that matters.
But then...
It’s not what you learn, but rather
what you do with what you learn
that matters.
Claudio	
  Perrone	
  
claudio@agilesensei.com	
  
www.agilesensei.com	
  
@agilesensei	
  
Join	
  the	
  book	
  no;fica;on	
  list!	
  
h#p://popcornflow.com/book	
  
Next is now

PopcornFlow: Continuous Evolution Through Ultra-Rapid Experimentation

  • 1.
    written, illustrated and performedby Claudio Perrone agilesensei.com @agilesensei Continuous evolution Through ultra-rapid experimentation
  • 2.
  • 3.
  • 4.
    He wants toget things done
  • 5.
  • 6.
    Be part ofa high-performance team
  • 7.
    Jim would liketo change the world
  • 8.
    But the world doesnot want to be changed
  • 9.
    His company wentthrough many reorganizations, only to stay the same Organization chart Blame flow Rule makers Controllers Enforcers VictimsOrganization chart God Losers
  • 10.
  • 11.
    most of us thinkabout change as big, slow and scary
  • 12.
    But what ifwe could make it infinitely small… … and learn to evolve almost as fast as a virus?
  • 13.
    “ -- 1stPopcornFlow Principle (aka “the virus” principle) If change is hard, make it continuous. Here is a “mad” thought…
  • 14.
    trying to rewirethe human brain is difficult, however.
  • 15.
    A better optionis to ACT ON THE system – i.e. the environment in which decisions are made. …But how?
  • 16.
  • 17.
    A while ago,I worked with a team who had not deployed software in months
  • 18.
    With the motto“Hard on systems, soft on people”, We worked together and evolved using the kanban method
  • 19.
    The Kanban boardcaptured our value stream… … But that’s only the outcome of our thinking
  • 20.
    “ -- ClaudioPerrone It’s not what you do but rather what you learn by doing it that matters. You see...
  • 21.
    Problems & observations Options Possible experiments OngoingReviewNext Committed thereal “secret” was our rapid stream of traceable change experiments…
  • 22.
    the real “secret”was our rapid stream of traceable change experiments… Problems & observations Options Possible experiments OngoingReviewNext Committed PopcornFlow Claudio Perrone PopcornFlow.com  h#p://agilesensei.com/resources   ... A powerful learning stream that I call “popcorn Flow”...
  • 23.
    So, we capturedour learning journey on a parallel “PopcornFlow board”
  • 24.
    It starts withProblems & Observations The quality of our code sucks.
  • 25.
  • 26.
    “Everybody is entitledto their own opinion, but… A shared opinion is a fact. … so, I’m happy to Make progress even with imperfect information. As a consequence… -- 2nd PopcornFlow Principle (aka “the kaizen urgency” principle)The quality of our code sucks.
  • 27.
    The quality of ourcode sucks. ...I use shared observations to create/elicit options (“rule of three”). Test-driven development Code review Pair Programming
  • 28.
    Test-driven development Code review Pair Programming Promising optionslead to a backlog of possible experiments. Action: Research good books on TDD Action: Let’s pair program for 3 days
  • 29.
    Action: Let’s pairprogram Reason: Code quality sucks Expectations: -  Perception is that code is better -  We’ll like it & want to keep doing it Duration: 3 days Review Date: dd/mm/yy experiments that we Commit to pursue have an action, reason, expectation and Review date.
  • 30.
    Experiment: "Fix asyou go": If found small bugs (less than 20mins), just branch and fix them. Do a pull request and mark the id on the card. Reason: too much bureaucracy for small bugs. Expectation: - developer happy to fix things as needed without lengthy triages. - steadily improving quality. - low bureaucracy, but still able to track it if things go wrong. - at least 3 bugs fixed like this by due date. Experiment: Pair on JIT analysisReason: We are moving towards JIT analysis to reduce sprint planning and moving to continuous flow.Expectation: - DoD created - Team agrees that analysis goes smoothly- No significant bottlenecks created Experiment: Do an Analytics meet-up to show how analytics work in <new kanban tool> Reason: <product owner> needs some form of predictability. Expectation: - Po/Team are aware of what’s possible now with the current level of analytics - We have better understanding of if, how, when we can improve forecasting with minimum amount of estimation.
  • 31.
    At Each retrospective,we ask exactly these questions: Action: Let’s pair program Reason: Code quality sucks Expectations: -  Perception is that code is better -  We’ll like it & want to keep doing it Duration: 3 days Review Date: dd/mm/yy
  • 32.
    Some people fear“failure”… Gap = Frustration Reality Expectation
  • 33.
    … But weonly really “fail” when we limit our opportunities to learn Gap = Frustration Reality Expectation Learning
  • 34.
    “ -- 3rdPopcorn Flow Principle (aka “the skateboarder” principle) It’s not “fail fast, fail often”… It’s “learn fast, learn often”. YOU SEE…
  • 35.
    Can you REALLY pretendthat you’ll never fall?
  • 36.
    Right from thebeginning, I knew this was different.
  • 37.
    ... Because theteam COULD easily handle 5-10 change experiments each week...
  • 38.
    ... rapidly enablingit to DELIVER multiple times a day
  • 39.
    …and then itspread. Popcorn boards started to appear in other parts of the organization.
  • 40.
    Imagine a continuousflow of experiments to dramatically accelerate the rate of change in every corner of your organization... ... How far would you go?
  • 41.
    Today, popcorn flowis entering more organizations
  • 42.
    It was designedto quickly introduce, sustain & accelerate change…
  • 43.
    … But then,I wondered: what jobs are other people ‘hiring’ PopcornFlow for?
  • 44.
    They “hire” aproduct or service to get the job done. Prof  Clayton  Christensen   People encounter situations that drive the need to accomplish a job. After all…
  • 45.
    Some teams ‘hire’Popcornflow to better reflect and continuously improve the way they work.
  • 46.
    others use itto reach product/market fit (e.g., “improve conversion rate from 5% to 10%”)
  • 47.
    corporate boardrooms useit for strategic decision-making (real options)
  • 48.
    PopcornFlow is touchinglives even outside the business world…
  • 49.
  • 50.
    ... Schools, autismsupport groups.
  • 51.
    PopcornFlow is evenpart of A proposal to foster innovation in the public sector
  • 53.
    popcorn Flow isalso getting traction at personal level
  • 54.
    “Every single week, I’m5 experiments older. Can I evolve even faster? Can you? Continuous evolution Is a way of life. -- Claudio Perrone
  • 55.
    Projects under activedevelopment include a lightweight “Action Deck” to facilitate face-to-face conversations... (... Which I used to help some friends finding a job)
  • 56.
    ...stickers, to setupa popcornflow board like a pro in minutes...  h#p://popcornflow.com/s;ckers   JUST   RELEASED!  
  • 57.
  • 58.
    (psst... a “secret”online platform...)
  • 59.
    ... And abook.  h#p://popcornflow.com/book   JOIN  THE   EARLY   NOTIFICATION   LIST!  
  • 60.
  • 61.
    “ -- Claudio Perrone It’snot what you do but rather what you learn by doing it that matters. But then... It’s not what you learn, but rather what you do with what you learn that matters.
  • 62.
    Claudio  Perrone   claudio@agilesensei.com   www.agilesensei.com   @agilesensei   Join  the  book  no;fica;on  list!   h#p://popcornflow.com/book   Next is now