Managing or leading a testing team is probably one of the most challenging positions in the IT industry. The team is usually understaffed, lacks appropriate tooling, and financing. Deadlines don’t move but the testing phase is continually being pressured by product delays. Motivation and retention of key testing personnel under these conditions is critical.

How do you accomplish this seemly impossible task? I can only go by my personal experience both as a lead and a team member:

• If the timelines are impacted, modify the Test Plan appropriately in terms of Scope.
• Clearly communicate the situation to the testing team and project management.
• Keep clear lines of communication to Development and project management.
• Whenever possible sell, sell, sell the importance and contributions of the Testing Team.
• Ensure the testing organization has clearly defined roles for each member of the team and a well-defined career path.
• Measure and communicate testing return on investment -- if the detected defect would have reached the field what would have been the cost.
• Explain testing expenditures in terms of investment (ROI) not cost.
• Finally, never lose your cool.

There are really two sides to testing Verification and Validation. Unfortunately the meaning of these terms has been defined differently by several governing / regulatory bodies. To put it more succinctly there is testing that can be performed before the product is constructed / built and there are types of testing that can be performed after the product has been constructed / built.

Preventing defects from occurring involves testing before the product is constructed / built. There are several methods for accomplishing this goal. The most powerful and cost effective being Reviews. Reviews can be either formal / technical reviews or peer reviews. Formal product development life cycles will provide the testing team with useful materials / deliverables for the review process. When properly implemented any effective development paradigm should supply these deliverables. For example:

• Cascade
• Requirements
• Functional Specifications
• Agile or Extreme
• High level Requirements
• Storyboards

Testing needs to be involved in this Review process and any defects need to be recorded and managed.