Growing Whole Team Quality

Fd80f9c58b06270d42356dd77a32defa?s=47 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.”

Fd80f9c58b06270d42356dd77a32defa?s=128

Jim Holmes

January 08, 2016
Tweet

Transcript

  1. Growing Whole Team Quality

  2. What’s Quality?

  3. Something of value to someone

  4. (Who will pay you for it)

  5. FDD / GDD

  6. Forrester Driven Development Gartner Driven Development

  7. SAMMWNRCTAUDD

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

    Driven Development
  9. Whole Team Quality Best Practice ISO- Standardized CMMI SCRUM-Certified Tip

    #0
  10. Build The Right Thing

  11. Who “Assures” Quality?

  12. “We’ll test quality in!”

  13. “No time to elaborate specs with you”

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

  15. “We only estimate dev time”

  16. Stakeholders

  17. (They’re bad kids!)

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

    #1
  19. Don’t Ask Be Awesome

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

  21. And people

  22. And money

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

    #2
  24. Learn What Stats Matter

  25. Why Change?

  26. Sometimes things are good enough

  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.
  28. Sometimes things are not good enough

  29. None
  30. Whole Team Quality Best Practice ISO- Standardized CMMI SCRUM-Certified Tip

    #3
  31. Start With Your Delivery Pipeline

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

    #4
  33. “Done” Means Working Software in Prod

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

    #5
  35. Pairing Isn’t Just For Devs

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

    #6
  37. Trumpet Your Wins

  38. Jim Holmes @AJimHolmes FrazzledDad.com

  39. bit.ly/leadershipjourney