ManyLessons Learned from 20 Years of               Managing Testing                                                   Joha...
Software Testing Has Nothing to do      with Product Quality...                 2
Software Testing Has Everything to do      with Product Information                  3
More Information Means More       Testing ApproachesThe more complex the problem, the more diversity youneed in testing  E...
How do You Provide Information?Weather reportTest dashboards                  5
No Traffic Lights!        6
Weather Report      7
Test Dashboard      8
Lesson: Software Testers Are Not            Victims!      Testers Have Power                9
Do You Have Enough People?How do you know?What is not getting done?                            10
End the MultitaskingHow many of you are context switching between several#1 priorities?  Do you confuse urgent and importa...
Yes Can Get You Into TroubleSaying ‘Yes’ leads you to agree to work you may not havethe people or time to do  And agreeing...
No is a Necessary Tool          13
No Can Get You Into TroubleIf you only say ‘No” or say ‘No’ in the wrong way or tothe wrong project, you can run into poli...
A Little Experiment         15
Maybe  16
Maybe is a DisasterThe people who want to hear “yes” will hear yesThe people who want to hear “no” will hear noAll of thos...
A Project Portfolio        18
Combination View:Low and Mid Level        19
Project Portfolio Explains StaffingWhat do you do if you don’t have enough people?     Victim mentality: Placate and do the...
Congruence    21
Many More Management LessonsInterpersonal skills such as feedback and coachingCreates an environment for success  Developi...
Congruence    23
Lesson: Software Release is a Business               Decision                   24
Testers Do Not Get to Judge the     Goodness of the Product.They Provide Information About the             Product.       ...
Release Criteria are Your Friend                26
Process != Testing         27
There’s More...On www.jrothman.comI’m @johannarothman on TwitterVisit http://www.jrothman.com to read more or sign up for ...
Upcoming SlideShare
Loading in …5
×

20 years.lessons.learned.key

801 views

Published on

Lessons I learned from years of testing, formally and informally

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

  • Be the first to like this

No Downloads
Views
Total views
801
On SlideShare
0
From Embeds
0
Number of Embeds
20
Actions
Shares
0
Downloads
10
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

20 years.lessons.learned.key

  1. 1. ManyLessons Learned from 20 Years of Managing Testing Johanna Rothman New: Manage Your Project Portfolio: Increase Your Capacity and Finish More Projects www.jrothman.com jr@jrothman.com 781-641-4046
  2. 2. Software Testing Has Nothing to do with Product Quality... 2
  3. 3. Software Testing Has Everything to do with Product Information 3
  4. 4. More Information Means More Testing ApproachesThe more complex the problem, the more diversity youneed in testing End-to-end system testing Combinatorial testing Feature-based testing to assess risk Area testing for developer feedback ... 4
  5. 5. How do You Provide Information?Weather reportTest dashboards 5
  6. 6. No Traffic Lights! 6
  7. 7. Weather Report 7
  8. 8. Test Dashboard 8
  9. 9. Lesson: Software Testers Are Not Victims! Testers Have Power 9
  10. 10. Do You Have Enough People?How do you know?What is not getting done? 10
  11. 11. End the MultitaskingHow many of you are context switching between several#1 priorities? Do you confuse urgent and important?You can only do one (important) thing at a timeIf you decide who is on what project, you must develop aproject portfolio 11
  12. 12. Yes Can Get You Into TroubleSaying ‘Yes’ leads you to agree to work you may not havethe people or time to do And agreeing to something on the spur of the moment might lead you to agree to something you don’t know anything aboutA True Story 12
  13. 13. No is a Necessary Tool 13
  14. 14. No Can Get You Into TroubleIf you only say ‘No” or say ‘No’ in the wrong way or tothe wrong project, you can run into political troubleA True Story 14
  15. 15. A Little Experiment 15
  16. 16. Maybe 16
  17. 17. Maybe is a DisasterThe people who want to hear “yes” will hear yesThe people who want to hear “no” will hear noAll of those people are your senior managers 17
  18. 18. A Project Portfolio 18
  19. 19. Combination View:Low and Mid Level 19
  20. 20. Project Portfolio Explains StaffingWhat do you do if you don’t have enough people? Victim mentality: Placate and do the project anyway Blame the developer-mentality: “If we had better people/ architecture/whatever, we wouldn’t need as many testers” Super-reasonable: “The standard for a dev to test ratio is ...”Congruence is explaining the needs of the project, the abilities andnumber of people, and the context of the organization. Use theproject portfolio to explain. 20
  21. 21. Congruence 21
  22. 22. Many More Management LessonsInterpersonal skills such as feedback and coachingCreates an environment for success Developing a strategy Leads the hiring Builds trusting relationships Build training time into the work week 22
  23. 23. Congruence 23
  24. 24. Lesson: Software Release is a Business Decision 24
  25. 25. Testers Do Not Get to Judge the Goodness of the Product.They Provide Information About the Product. 25
  26. 26. Release Criteria are Your Friend 26
  27. 27. Process != Testing 27
  28. 28. There’s More...On www.jrothman.comI’m @johannarothman on TwitterVisit http://www.jrothman.com to read more or sign up for my emailnewsletter. Or give me your card. Or fill out a yellow form. 28

×