Effective Testing Techniques
By Denise DeCarlo, PMP

As we all know, we NEVER have enough time for testing. Because testing typically comes as the end of the project lifecycle, any delays from deliverables in the early phases of the project impact the testing efforts. The amount of time to test is usually reduced to meet a promised end date provided to our customers and sponsor. By reducing the testing time, this brings risk to the project by jeopardizing the quality and stability of the product when it is implemented. The trick to good testing is doing it EARLY in the project lifecycle and to perform testing efficiently and effectively. Working with your customer early in the project to derive a MANDATORY set of tests that must be performed can also alleviate some of the pressure to “cut corners”.

The following techniques will enable you to test critical product deliverables for accuracy and completeness:

• Take walkthroughs/reviews SERIOUSLY. This is a great opportunity for you to “test” the product EARLY in the project lifecycle. Types of documents that should be reviewed thoroughly include: requirements, high level design, detail design, technical specifications, business process models, user training materials, site maps, and any other key paper products that are produced. An ideal walkthrough will have 10 or less people, it will have the RIGHT people at the meeting, and follows a clear agenda. Attendees should be required to review the documentation PRIOR to the meeting. Cancel walkthroughs if you don’t get the right attendees and/or if people have not had time to review the documentation ahead of time. There is no sense in wasting time by having a walkthrough if the meeting only serves to give people a chance to review the material. The project manager should ensure the walkthrough is EFFECTIVE – not just a checkmark to say a requirement that is part of the company’s methodology has been completed.

• Ensure that walkthroughs are managed with a checklist to ensure corporate standards are being followed and provide a guideline of items to look for in a “good” product. It is one thing to find deficiencies in a product, but it is much more effective if a standard is established for product quality. Have several different people review product deliverables for accuracy and thoroughness. This should include people from various business units, different hierarchical levels within the organization, and technical experts.

• Establish few approvers. Having too many approvers slows down the process. Two to three approvers maximum per deliverable is recommended.

• Provide templates of good product deliverables that have been produced for other projects. People can mimic a good document and apply their expertise for the document they are trying to create.

continue>>