Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Growing Whole Team Quality

Jim Holmes
January 08, 2016

Growing Whole Team Quality

Presented at CodeMash 2016.

Organizational change doesn’t come easy. We humans are tetchy beings who often aren’t comfortable getting out of the comfy ruts we let ourselves get in. Join Jim Holmes for an experience report on how he helped a couple organizations change how they tested and delivered software. You’ll learn some critical techniques for helping drive change around testing: Getting buy-in from executives and management. Hiring/staffing the right people. Helping existing team members learn to adapt–and dealing with those that won’t. You’ll also learn why testing tools and test cases do NOT solve any quality issues, and you’ll also hear plenty of lessons-learned and hard knocks. Stovepiped testing should have gone down with the Titanic. Learn how to help your organization get quality across your entire delivery team, not just the people you blame for not “Assuring Quality.”

Jim Holmes

January 08, 2016
Tweet

More Decks by Jim Holmes

Other Decks in Programming

Transcript

  1. Growing Whole Team
    Quality

    View Slide

  2. What’s Quality?

    View Slide

  3. Something of value to
    someone

    View Slide

  4. (Who will pay you for it)

    View Slide

  5. FDD / GDD

    View Slide

  6. Forrester Driven
    Development
    Gartner Driven
    Development

    View Slide

  7. SAMMWNRCTAUDD

    View Slide

  8. Stupid-Assed Marketing
    Mafia With No Real
    Connection To Actual
    Users Driven
    Development

    View Slide

  9. Whole Team Quality
    Best Practice ISO-
    Standardized CMMI
    SCRUM-Certified
    Tip #0

    View Slide

  10. Build The Right Thing

    View Slide

  11. Who “Assures” Quality?

    View Slide

  12. “We’ll test quality in!”

    View Slide

  13. “No time to elaborate specs
    with you”

    View Slide

  14. “It won’t really take you that
    long”

    View Slide

  15. “We only estimate dev time”

    View Slide

  16. Stakeholders

    View Slide

  17. (They’re bad kids!)

    View Slide

  18. Whole Team Quality
    Best Practice ISO-
    Standardized CMMI
    SCRUM-Certified
    Tip #1

    View Slide

  19. Don’t Ask
    Be Awesome

    View Slide

  20. Skunkworks is fine, but
    at some point you need
    support

    View Slide

  21. And people

    View Slide

  22. And money

    View Slide

  23. Whole Team Quality
    Best Practice ISO-
    Standardized CMMI
    SCRUM-Certified
    Tip #2

    View Slide

  24. Learn What Stats
    Matter

    View Slide

  25. Why Change?

    View Slide

  26. Sometimes things are good
    enough

    View Slide

  27. Well, you should always be
    continuing to learn and improve
    which is of course obvious because
    what I was really talking about was
    major overhauls in which case
    sometimes that doesn’t make sense
    if your organization is generally
    happy and your customers are
    good and you have bacon.

    View Slide

  28. Sometimes things are
    not
    good enough

    View Slide

  29. View Slide

  30. Whole Team Quality
    Best Practice ISO-
    Standardized CMMI
    SCRUM-Certified
    Tip #3

    View Slide

  31. Start With Your
    Delivery Pipeline

    View Slide

  32. Whole Team Quality
    Best Practice ISO-
    Standardized CMMI
    SCRUM-Certified
    Tip #4

    View Slide

  33. “Done” Means
    Working Software in
    Prod

    View Slide

  34. Whole Team Quality
    Best Practice ISO-
    Standardized CMMI
    SCRUM-Certified
    Tip #5

    View Slide

  35. Pairing Isn’t Just For
    Devs

    View Slide

  36. Whole Team Quality
    Best Practice ISO-
    Standardized CMMI
    SCRUM-Certified
    Tip #6

    View Slide

  37. Trumpet Your Wins

    View Slide

  38. Jim Holmes
    @AJimHolmes
    FrazzledDad.com

    View Slide

  39. bit.ly/leadershipjourney

    View Slide