Pro Yearly is on sale from $80 to $50! »

Neuroscience and Kanban

Neuroscience and Kanban

Visual Management with the brain in mind.
A talk on Chillisoft's research using principles of Neuroscience to design Kanban boards and the lessons we learnt along the way.

This talk was presented @ Durban Agile User Group May 2015

6b4b1103398f0ba66ceafb1afb19e33f?s=128

Travis Frisinger

May 28, 2015
Tweet

Transcript

  1. Neuroscience and Kanban Visual Management with the brain in mind

  2. About Me • Team lead at Chillisoft • MSc in

    Software Engineering • Neuroleadership Certificate • Not Canadian
  3. Context • The challenge of delivering and managing

  4. Breakdown • The Brain • Neuroleadership • Agile and Lean

    Principles Review • Neuro-Kanban Experimentation
  5. The Brain A quick overview, I promise.

  6. The Brain • Limbic System • System 1

  7. The Brain • PFC • System 2

  8. The Amygdala Hijack

  9. Back to Normal Programming

  10. Linking Neuroscience to Agile • SCARF • Jenni Jepsen on

    “The Neuroscience Behind Why Agile Works” • She states why David Rock’s SCARF model is behind Agile’s success. • http://www.scarf360.com/ • http://www.infoq.com/interviews/jepsen-why-agile-works
  11. SCARF • S - Status • C - Certainty •

    A - Autonomy • R - Relatedness • F - Fairness
  12. Agile and Lean Principles Review

  13. What is Agile • Agile is one of the big

    buzzwords of the IT development industry • Put simply, agile development is a different way of managing IT development teams and projects.
  14. 10 Key Agile Principles 1. Active user involvement is imperative

    2. The team must be empowered to make decisions 3. Requirements evolve but the timescale is fixed 4. Capture requirements at a high level; lightweight & visual 5. Develop small, incremental releases and iterate 6. Focus on frequent delivery of products 7. Complete each feature before moving on to the next 8. Apply the 80/20 rule 9. Testing is integrated throughout the project lifecycle – test early and often 10. A collaborative & cooperative approach between all stakeholders is essential
  15. What is Lean Software Development? • Adapted from the Toyota

    Production System • The term lean software development originated in a book by the same name, written by Mary Poppendieck and Tom Poppendieck
  16. 7 Lean Principles 1. Eliminate Waste 2. Build Quality In

    3. Create Knowledge 4. Defer Commitment 5. Deliver Fast 6. Respect People 7. Optimise The Whole
  17. Kanban Board Principles • Visualize workflow • Limit work-in-progress •

    Pull work from column to column • Monitor, adapt, improve Board Flow
  18. Kanban Board Principles • R2L-4-L2R Board Flow

  19. Information Radiators

  20. Defer Commitment vs Complete Each Feature • 70/30 rule •

    Eisenhower task matrix
  21. Delivery Expectations • Stanford Prison Experiment • Honesty is Accuracy

  22. Sticky Refactoring • The process of extracting the delivered value

    from a sticky.
  23. Defining Value • Autonomy • Finding Rabbit Holes

  24. Fluffy the Scrum Slayer

  25. Principles of ABD • Honesty is Accuracy • Your board

    must always reflect reality no matter how much it sucks! • Sticky Refactoring • Love your Technical Debt • By loving it you care about it, when you care about it you make sure it is taken care of. • Red Bins
  26. Our Real Boad

  27. Thank you! Questions? Social Media: • Twitter - @tmfrisinger •

    G+ - https://plus.google.com/+TravisFrisinger