Let Go Knowing: How Holding onto Views May Be Holding You Back - Mile High Agile 2015

008d9a555e3c3d1962761425b0e65a1e?s=47 Mike Cohn
April 03, 2015

Let Go Knowing: How Holding onto Views May Be Holding You Back - Mile High Agile 2015

You undoubtedly have a firmly held set of convictions about what is necessary to do agile well. These convictions have served you well—your teams have delivered better products more quickly and more economically than before they were agile. But could some of your firmly held convictions be holding you back? And have you ever wondered why some of your most agile friends are similarly firm in their own opinions—even ones that are the exact opposite of your own?

In this session, you’ll see ways that biases may be preventing you from questioning your assumptions, why being open to new views is hard but vital, and why beginners so often think they know it all. After this session, you will know how to discern the inviolate rules of Scrum from its merely good practices. You’ll know why you feel certain of some aspects of agile, less so about others. You’ll leave with the confidence to let go of knowing. And when we let go of knowing, we open ourselves to learning, which is the heart of agile.

008d9a555e3c3d1962761425b0e65a1e?s=128

Mike Cohn

April 03, 2015
Tweet

Transcript

  1. 1.

    Mike Cohn Mile High Agile April 3, 2015 Let Go

    of Knowing: How Holding onto Views May Be Holding You Back
  2. 4.
  3. 9.

    “We do waterfall, but we test all the time.” “We

    do waterfall, but we integrate weekly.”
  4. 12.

    “A mind is like a parachute. It doesn’t work if

    it’s not open.“ —Frank Zappa
  5. 15.
  6. 16.
  7. 17.
  8. 23.

    “Who does such-and-such in Scrum?” “When you’re teaching, always assume

    there is a silent student in the class who knows more than you do.” —Leo Strauss
  9. 25.

    ComparativeAgility.com False Mostly False Not True or False Mostly True

    True Management sets goals but doesn't tell team members how to achieve them. All bugs are fixed during the sprint in which they are found.
  10. 26.

    Seven dimensions • Teamwork • Requirements • Planning • Technical

    practices • Quality • Culture • Knowledge creation • Is the product owner involved in identifying acceptance criteria? • Are tests automated? • Are testers involved early?
  11. 27.

    Quality False Mostly False Not True or False Mostly True

    True Timing 2 years 6 months Acceptance tests Timing Quality focus
  12. 30.
  13. 31.

    Sample Scrum rules • Sprints cannot be longer than a

    month. • Be done with something by the end of the sprint. • Meet at the start of the sprint to discuss what you’ll do during the sprint. Do these
 or else!!
  14. 33.

    Test-Driven Development Pair Programming Sprint 0 Definition of Done User

    Stories Don’t Start Sprints on Mondays Product Backlog Refinement (Grooming) Practices Task Boards
  15. 35.

    “In science it often happens that scientists say, ‘You know,

    that's a really good argument, my position is mistaken,’
  16. 36.

    and then they actually change their minds, and you never

    hear that old view from them again. They really do it.
  17. 37.

    It doesn't happen as often as it should, because scientists

    are human and change is sometimes painful.
  18. 38.

    But it happens every day. 
 I cannot recall the

    last time something like that happened in politics or religion.”
 —Carl Sagan