Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

PopcornFlow: Continuous Evolution Through Ultra-Rapid Experimentation

16,625 views

Published on

This is a new method I invented to quickly introduce, sustain & accelerate change. Someone called it "The next big thing in Agile". I believe him :)

Published in: Business

PopcornFlow: Continuous Evolution Through Ultra-Rapid Experimentation

  1. 1. written, illustrated and performed by Claudio Perrone agilesensei.com @agilesensei Continuous evolution Through ultra-rapid experimentation
  2. 2. This…
  3. 3. … Is jim
  4. 4. He wants to get things done
  5. 5. Grow
  6. 6. Be part of a high-performance team
  7. 7. Jim would like to change the world
  8. 8. But the world does not want to be changed
  9. 9. His company went through many reorganizations, only to stay the same Organization chart Blame flow Rule makers Controllers Enforcers VictimsOrganization chart God Losers
  10. 10. So, Today, this is Jim.
  11. 11. most of us think about change as big, slow and scary
  12. 12. But what if we could make it infinitely small… … and learn to evolve almost as fast as a virus?
  13. 13. “ -- 1st PopcornFlow Principle (aka “the virus” principle) If change is hard, make it continuous. Here is a “mad” thought…
  14. 14. trying to rewire the human brain is difficult, however.
  15. 15. A better option is to ACT ON THE system – i.e. the environment in which decisions are made. …But how?
  16. 16. ARCHITECTING CHANGE (with PopcornFlow) @agilesensei
  17. 17. A while ago, I worked with a team who had not deployed software in months
  18. 18. With the motto “Hard on systems, soft on people”, We worked together and evolved using the kanban method
  19. 19. The Kanban board captured our value stream… … But that’s only the outcome of our thinking
  20. 20. “ -- Claudio Perrone It’s not what you do but rather what you learn by doing it that matters. You see...
  21. 21. Problems & observations Options Possible experiments OngoingReviewNext Committed the real “secret” was our rapid stream of traceable change experiments…
  22. 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. 23. So, we captured our learning journey on a parallel “PopcornFlow board”
  24. 24. It starts with Problems & Observations The quality of our code sucks.
  25. 25. inertia is our enemy…
  26. 26. “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.
  27. 27. The quality of our code sucks. ...I use shared observations to create/elicit options (“rule of three”). Test-driven development Code review Pair Programming
  28. 28. 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
  29. 29. 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.
  30. 30. 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.
  31. 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. 32. Some people fear “failure”… Gap = Frustration Reality Expectation
  33. 33. … But we only really “fail” when we limit our opportunities to learn Gap = Frustration Reality Expectation Learning
  34. 34. “ -- 3rd Popcorn Flow Principle (aka “the skateboarder” principle) It’s not “fail fast, fail often”… It’s “learn fast, learn often”. YOU SEE…
  35. 35. Can you REALLY pretend that you’ll never fall?
  36. 36. Right from the beginning, I knew this was different.
  37. 37. ... Because the team COULD easily handle 5-10 change experiments each week...
  38. 38. ... rapidly enabling it to DELIVER multiple times a day
  39. 39. …and then it spread. Popcorn boards started to appear in other parts of the organization.
  40. 40. Imagine a continuous flow of experiments to dramatically accelerate the rate of change in every corner of your organization... ... How far would you go?
  41. 41. Today, popcorn flow is entering more organizations
  42. 42. It was designed to quickly introduce, sustain & accelerate change…
  43. 43. … But then, I wondered: what jobs are other people ‘hiring’ PopcornFlow for?
  44. 44. 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…
  45. 45. Some teams ‘hire’ Popcornflow to better reflect and continuously improve the way they work.
  46. 46. others use it to reach product/market fit (e.g., “improve conversion rate from 5% to 10%”)
  47. 47. corporate boardrooms use it for strategic decision-making (real options)
  48. 48. PopcornFlow is touching lives even outside the business world…
  49. 49. e.g. Families,
  50. 50. ... Schools, autism support groups.
  51. 51. PopcornFlow is even part of A proposal to foster innovation in the public sector
  52. 52. popcorn Flow is also getting traction at personal level
  53. 53. “Every single week, I’m 5 experiments older. Can I evolve even faster? Can you? Continuous evolution Is a way of life. -- Claudio Perrone
  54. 54. 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)
  55. 55. ...stickers, to setup a popcornflow board like a pro in minutes...  h#p://popcornflow.com/s;ckers   JUST   RELEASED!  
  56. 56. h#p://discuss.popcornflow.com   … A discussion forum
  57. 57. (psst... a “secret” online platform...)
  58. 58. ... And a book.  h#p://popcornflow.com/book   JOIN  THE   EARLY   NOTIFICATION   LIST!  
  59. 59. Final Thoughts
  60. 60. “ -- 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.
  61. 61. Claudio  Perrone   claudio@agilesensei.com   www.agilesensei.com   @agilesensei   Join  the  book  no;fica;on  list!   h#p://popcornflow.com/book   Next is now

×