I'm at StarWest in Anaheim, CA this week. Thanks to those of you who attended my tutorial session on Monday on "Becoming an Influential Test Team Leader." We had a great time.
Some of you have asked for the list of testing challenges we made during the session, so here it is (not in any particular order):
1. Getting the right technology match (i.e., test tools) for the type of testing at hand
2. Not having enough time for testing
3. Lack of testing skills/training
4. Inability to reproduce defects
5. Insufficient documentation
6. Changing requirements
7. Knowing when to stop testing
8. Cultural resistance to testing
9. Lack of time for training
10. Holding back defect information to look good later in the project
11. Testers being seen as an obstacle to progress
12. No time reserves
13. Over-reliance on testing to find all the defects
14. Lack of human resources
15. Testing only along a narrow path (lack of rigor in testing)
16. Schedule-driven projects
17. The wrong people performing testing
18. Communication gaps
19. Resource planning
20. Non-tangible nature of QA/test
21. Transitioning to automation
22. Understanding how customers use a product
23. Managing offshoring of testing
Whew! What a list!
We determined that 18 are human in nature, 1 (#1) was purely technical and 4 were both. So, this validates the thesis of my book, Surviving the Top Ten Challenges of Software Testing, that most testing problems are people problems.
I'll check in later this week and give my thoughts on what I am hearing and seeing at the conference.
Randy Rice's Software Testing & Quality Blog