Testing Outsourcing: How It Can Work

Software testing outsourcing: How it can be done

• Pre-contract stage
• Contract stage
• Preparation stage
• Execution stage - Pilot project
• Execution stage - Basic project
• Acceptance stage
• Post-acceptance stage

I. Pre-contract stage

1. First contact. It is usually made by e-mail or phone.
2. Preliminary discussion of your testing needs or task. If it is required, NDA can be signed. You can use
   • E-mail, telephone, VoIP, IMs to talk over project details;
   • Audio or video conferences to interview our staff;
   • Meetings of your and our specialists on your site;
   • Visits to our office to examine our production capabilities.
     
     Please take into account that it is easy to reach us:
        - There is a good transport and tourist infrastructure in Ukraine;
        - There are no visa restrictions for the US and EU citizens;
        - Time difference for the EU countries is 1-2 hours only.
3. Basing on the information received from you, we will
   • Prepare our vision of the project (preliminary test strategy, project/test plan);
   • Evaluate resources (personnel, devices, tools, etc.) requisite for the project;
   • Estimate project feasibility;
   • Calculate a tentative cost sheet
   and discuss all of that with you.
4. We also provide you with information about previous projects, references, profiles and other data which can help you to make a well-grounded decision.
5. Our staff speaks English, German speaking co-workers are available too.
6. Please note: If you have any questions or doubts do not hesitate to contanct us. All your questions are welcome and appreciated. Remember: there are NO wrong questions for us.

II. Contract stage

1. It is a very responsible phase. So, both sides should pay sufficient attention to it. BugHuntress QA Lab understands that the customers live in the fast-paced and quickly changing business environment. That is why BugHuntress QA Lab proposes flexible contract terms that allow mutually acceptable modifications during project execution. BugHuntress QA Lab tries to build relations with customers on a partnership basis.
2. Preparation and signing a contract. BugHuntress QA Lab part is represented by its office in the USA (US-based full-registered company situated in New York). As a result, all BugHuntress QA Lab contracts are under the US legislation and assume proper legal guarantees.
3. NDA and other documents preparation and signing to provide the requisite legal background for informational security and IP rights protection.

Fig. 1. The scheme of interaction between the customer, development team(s) and BugHuntress QA Lab.

III. Preparation and planning stage

1. Communication and management procedures adjustment (who, how, when, how often).
2. Project plan, requirements specification, testing strategy and plans preparation and approval (for more details see BugHuntress software testing methodology).
3. Knowledge transfer - software/hardware to be tested, documentation and other necessary information, scripts (if any) transfer and deployment.
4. Project team trainings (if necessary) - it can be done on the customer's site, in training centers, on BugHuntress QA Lab site.
5. Technical and organizational measures to provide a necessary level of security and IP rights protection (if necessary):
   • Creation of a separate local network for a specified project;
   • Allocation of a dedicated server for the project;
   • Movement of the project participants into a separate room, etc.
6. Project infrastructure preparation:
   • Shared (online) management tools preparation (collaborative work tools, personnel control tools, etc.);
   • Shared (online) reporting tools adjustment (bug trackers, etc.);
   • Communication channels establishment (VPN, IMs, etc.);
   • Fulfillment of configuration management activities.
7. Preparation of testing infrastructure:
   • Deployment of automated testing tools (if necessary);
   • Development of additional (to standard off-the-shelf tools) automated testing tools, emulators, etc. (if necessary);
   • Relevant specific hardware/ software/ network/ mobile devices purchasing, installation, setting up;
   • Environment preparation for performance, load, stress, etc. testing.

IV. Execution stage - Pilot project

1. This stage is very important. Its goal is to check the level of vendor's services in practice, study the management style and estimate possibilities to work together.
2. Tests execution.
3. Routine reports (on a weekly or daily basis).
4. Regular discussion of the project progress. As an option a dedicated (SQA) manager on the customer's site can be assigned for continuous project overseeing and resolution of routine questions. Problems discussing and resolving (if necessary).
5. Delivery, acceptance and approval.
6. Payment(s) for the pilot project under the contract terms.
7. Pilot project analysis. Making a decision regarding next steps.

V. Execution stage - Basic project

1. Tests execution.
2. Routine reporting (on a weekly or daily basis). Bug reports are usually delivered on a daily basis (or even more often) because a testing team works in close interaction with a development team. Nonetheless, some types of testing can imply another than daily delivery schedule.
3. Note: We offer flexible business models. If necessary, you can resize the testing team (add or reduce team members), change technologies, etc.
4. Regular discussion of the project progress. Tracking and management of requirements changes. Questions/problems discussing and resolving (if necessary).
5. Communicate. Feel free to ask, specify and check. We strongly believe that questions which are timely revealed, frankly discussed and resolved are inevitable challenges of any business. Only problems which are not timely brought up can become stubborn issues.
6. Intermediate acceptance and payments (according to the contract terms).
7. Intermediate analysis and recommendations for next phases.

VI. Acceptance stage

1. Final delivery. Final report and recommendations regarding software quality and its enhancement.
2. Customer acceptance and approval. Final payment.
3. Project acceptance (internal BugHuntress QA Lab meeting): bottom line, conclusions and recommendations for the future projects.

VII. Post-acceptance stage

1. Testimonials and references.
2. Repeat business (more than 30% of BugHuntress customers do so) and/or ongoing long-time mutually beneficial partnership.