Doing Agile Isnt The Same As Being Agile

12,935 views
12,648 views

Published on

Presented to XPNYC and PHXSUG in January 2010.

Published in: Technology, Business
0 Comments
52 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
12,935
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
0
Comments
0
Likes
52
Embeds 0
No embeds

No notes for slide
  • Do you have daily standups? Do you use planning poker or another collaboration technique for sizing? Do you use a big visible board of some sort to track status of your iterations? Or if you are using Kanban do you have the board clearly visible by everyone? Are you doing iterations at all? How about iteration demonstrations? How about retrospectives?
  • Are you doing daily stand-up meetings? Is the voice of the customer represented? Do you work in iterations? Do you demonstrate working software? Do you do retrospectives? Are you pair programming? Are you doing test-driven development? Is your team cross-functional?
  • Have you increased productivity, stakeholder satisfaction, or quality? Have you reduced time-to-market? Have you increased ROI?
  • Is agile a tool to help you get thee results you want/need, or…
  • Are you blindly following the practices every iteration because that is how you were taught?
  • Boring daily stand-up Lengthy planning meetings Dropping stories each iteration Code freezes for testing …
  • Doing agile means you keep doing the same thing over and over again while expecting a different result. What’s that called? Insanity!
  • Product, dev, QA
  • Doing Agile Isnt The Same As Being Agile

    1. 1. Doing Agile isn’t the same as BEING Agile!!! Presented by Bob Hartman Certified Scrum Coach Agile For All Web: www.agileforall.com Blog: www.agilebob.com
    2. 2. Bob Hartman (Agile Bob) <ul><li>30+ years of software industry experience </li></ul><ul><li>Certified Scrum Coach (CSC) </li></ul><ul><li>Bachelor and Masters degrees in Computer Science </li></ul><ul><li>Roles included Tester, Developer, Dev Manager, QA Manager, Product Manager, Project Manager, VP… </li></ul><ul><li>Started with agile in 1999 </li></ul>[email_address] 303-766-0917 blog: www.agilebob.com Doing Agile isn’t the Same as BEING Agile
    3. 3. Is your organization doing agile? Doing Agile isn’t the Same as BEING Agile
    4. 4. What do you consider doing agile? Doing Agile isn’t the Same as BEING Agile
    5. 5. Are you doing agile better now than when you started doing agile? Doing Agile isn’t the Same as BEING Agile
    6. 6. Awesome! It sounds like doing agile is working for many of you! Doing Agile isn’t the Same as BEING Agile
    7. 7. … or is it? Doing Agile isn’t the Same as BEING Agile
    8. 8. Is agile working for you … AGILE Doing Agile isn’t the Same as BEING Agile
    9. 9. … or are you a slave to it? AGILE Doing Agile isn’t the Same as BEING Agile
    10. 10. Any of these look familiar? Doing Agile isn’t the Same as BEING Agile Stories committed 15 15 13 Stories accepted 10 9 8
    11. 11. How long has it been like that? Doing Agile isn’t the Same as BEING Agile
    12. 12. Why is little to no progress ok? Doing Agile isn’t the Same as BEING Agile
    13. 13. Because DOING agile hits a brick wall Doing Agile isn’t the Same as BEING Agile
    14. 14. Randy Pausch on brick walls “ Brick walls are there for a reason. The brick walls are not there to keep us out. The brick walls are there to show how badly we want something. Because the brick walls are there to stop the people who don’t want something badly enough. They are there to keep out the other people.” – from “The Last Lecture” Doing Agile isn’t the Same as BEING Agile
    15. 15. How do you get through the wall? Doing Agile isn’t the Same as BEING Agile
    16. 16. One answer: Raise the wall off the ground Need a foundation to support raising the wall Doing Agile isn’t the Same as BEING Agile
    17. 17. Go back to the foundations of agile Doing Agile isn’t the Same as BEING Agile
    18. 18. One foundation: The Agile Manifesto Doing Agile isn’t the Same as BEING Agile
    19. 19. Another foundation: Lean thinking Doing Agile isn’t the Same as BEING Agile
    20. 20. A 3 rd foundation: Common sense! RIP Doing Agile isn’t the Same as BEING Agile
    21. 21. Thinking agile + doing agile = being agile Doing Agile isn’t the Same as BEING Agile
    22. 22. Top 10 ways to “think agile” AGILE Doing Agile isn’t the Same as BEING Agile From the home office in Aurora, Colorado…
    23. 23. #10: Think small. No, smaller! Doing Agile isn’t the Same as BEING Agile
    24. 24. #9: Ask “How will we improve?” Then do it! Doing Agile isn’t the Same as BEING Agile
    25. 25. #8: Collaborate. No, really. Collaborate! Doing Agile isn’t the Same as BEING Agile
    26. 26. #7: Ask “What does the team think?” OUR Doing Agile isn’t the Same as BEING Agile
    27. 27. #6: Always, always, always think about… Doing Agile isn’t the Same as BEING Agile
    28. 28. #6: Root cause, not band-aids Doing Agile isn’t the Same as BEING Agile
    29. 29. #4: Failure is ok (with 3 conditions) Doing Agile isn’t the Same as BEING Agile
    30. 30. #3: Measure influence not control Span of control (dev) – items directly controlled Span of influence – must have teamwork and rely on others to succeed Span of control (dev): Coded story points Span of control (QA): Number of tests run Span of influence: Features in the field with no reported bugs in 90 days Span of control (QA) – items directly controlled Doing Agile isn’t the Same as BEING Agile
    31. 31. #2: Have 3 headed conversations Doing Agile isn’t the Same as BEING Agile
    32. 32. Doing Agile isn’t the Same as BEING Agile Ask: How can we have the ability to accept stories every single day of every single iteration and know the whole system still works correctly all the time?
    33. 33. Brainstorm time! <ul><li>What other questions would you ask in order to get a team to start “thinking” agile? </li></ul><ul><li>What other helpful phrases could you use to start “thinking” agile? </li></ul>Doing Agile isn’t the Same as BEING Agile
    34. 34. Leading causes of agile failure <ul><li>A dysfunctional Product Owner (or equivalent in non-Scrum frameworks) </li></ul><ul><li>Lack of automated testing </li></ul><ul><li>Lack of training and agile experience </li></ul><ul><li>Inability to change corporate culture </li></ul><ul><li>Not continuing to improve over time </li></ul><ul><li>Going through the motions without knowing WHY! </li></ul>Doing Agile isn’t the Same as BEING Agile
    35. 35. Doing Agile isn’t the Same as BEING Agile
    36. 36. Does Ken Schwaber have it right? Doing Agile isn’t the Same as BEING Agile
    37. 37. I think he does … Doing Agile isn’t the Same as BEING Agile
    38. 38. … but using isn’t the same as BEING! Doing Agile isn’t the Same as BEING Agile
    39. 39. A final key thought Doing Agile isn’t the Same as BEING Agile
    40. 40. Oops, let me be agile about that Doing Agile isn’t the Same as BEING Agile As a team We want to be transparent So that we can inspect closely and adapt meaningfully User Story
    41. 41. One more time for the BDD folks Doing Agile isn’t the Same as BEING Agile Acceptance Criteria Given that we are being transparent When we inspect closely Then we should be able to adapt meaningfully
    42. 42. Goal: Plan… Do… Check… Act… Repeat with improvement! Doing Agile isn’t the Same as BEING Agile
    43. 43. Doing Agile isn’t the Same as BEING Agile
    44. 44. Doing Agile isn’t the Same as BEING Agile Bob Hartman Certified Scrum Coach Agile For All 303-766-0917 [email_address] Web: www.agileforall.com Blog: www.agilebob.com

    ×