A well made test plan is the key to a successful test project.

All aspects of the software under test have to be defined. Also those aspects that will be outside of the scope. This to avoid confusion at the end of the test project. 
After execution of the test plan, the testers will be "discharged".

We feel that every test plan should minimally have the following components / chapters:

• Description of the "Software under test"
• Responsibilities of the organization, test team, supplier, development team etc..
• Decision process
• Planning
• Test types and techniques
• Go/No go criteria and the basis of setting priorities and how to manage the project
• Metrics to be used 
• Progress reporting
• Test report / Fitness for use (Go/NoGo)

In order to execute a test plan, the availability of the right software testers is of utmost importance. Every project has it's own challenges in architecture, security, business knowledge and tooling to be used.

For over 17 years, as a company, we have in depth knowledge of

• Setting up test plans and project plans
• Selection of the right testers (both internal and external resources).

Please contact us, to show you how we could save you money by:

• Making the right test plan
• Making a choice from our library of test plans
• Selecting the right staff for your project