007 ‐ Live Project (Part 1) ‐ How a Project begins - rkb-sdet/SoftwareTesting GitHub Wiki

Session 7 – Live Project (Part 1): How a Software Testing Project Begins

1. Introduction

This session explains the Independent Software Testing Project process, focusing on how a project starts in a real company scenario.

2. What is an Independent Software Testing Project?

  • Independent Software Testing Company:
    • Provides only software testing services (no development or other services).
    • Example: XYZ Company is an independent testing company.
  • Client Company:
    • Owns the application that needs testing.
    • Approaches the independent testing company for testing services.
  • Independent Project:
    • Performed entirely by the independent software testing company.
    • Only testing services are provided to the client.

3. Case Study Structure

This is one example (case study) — actual processes may vary across companies.

  • XYZ Company: Independent software testing company.
  • Client Company: Has an application needing testing.
  • You: A software tester at XYZ Company.

4. How the Project Begins

4.1 Business/Sales Team

  • Purpose: Get new projects by marketing testing services.

  • Hierarchy (example structure):

    1. Business Development Manager
    2. Business Development Leads
    3. Senior Business Development Executives (BD)
    4. Business Development Executives (BDE)

  • Role of BDE:

    • Market the company’s testing services.
    • Find leads, send marketing emails, and contact potential clients.
    • Respond to inbound client requests.
    • Convert a lead into a kick-off meeting opportunity.

4.2 Lead to Kick-Off Meeting

  1. Client expresses interest (“We need your testing services.”).
  2. BDE schedules a kick-off meeting:
    • Asks client for availability.
    • Coordinates date & time.
  3. Meeting attendees:
    • From XYZ Company: BDE (mediator), Test Manager, possibly Test Lead, and other testers.
    • From Client: Client-side representatives.

4.3 Company Testing Team Structure

  • Test Manager: Oversees multiple projects, manages leads.
  • Test Leads: Lead individual projects.
  • Senior Test Engineers: Experienced testers.
  • Test Engineers: Execute test cases and report defects.

5. Kick-Off Meeting Steps

Step 1 – Introduction

  • BDE welcomes client and introduces the testing team.
  • May give high-level overview of:
    • Company profile
    • Offered testing services
    • Experience, clients, and capabilities

Step 2 – Client Requirements

  • Test Manager asks:
    • What type of testing is required? (Manual, Automation, API, Database, Security, Performance, etc.)
    • Application details and purpose
    • Number of resources needed
    • Any special working conditions or schedules
    • Billing expectations and timelines

Step 3 – Application Demo

  • Client may:
    • Demonstrate the application (if available).
    • Provide documentation (Requirement docs, Help docs, Mock Screens, Flow diagrams).
    • Explain specific testing needs.
    • Mention constraints or special instructions.

Step 4 – Proposal Preparation

  • After the meeting:
    • BDE follows up to collect all promised documents.
    • Test Manager prepares a proposal including:
      • Company introduction & services offered
      • Project-specific testing services
      • Billing model & rates
      • Number and type of resources (Leads, Senior Testers, Testers)
      • Working hours & timelines
      • Testing approach/strategy
      • Next steps

Step 5 – Agreement

  • If client accepts the proposal:
    • Formal agreement is signed between the client and the independent testing company.
    • Without a signed agreement, the project does not start.

6. Post-Agreement

  • Project officially begins.
  • First task: Exploring the application.
  • BDE exits — from here, Test Manager & team directly communicate with the client.

7. Key Takeaways

  • Independent Software Testing Project means only testing services are offered.
  • BDE role ends once the lead is converted into a signed project.
  • Kick-off meeting is critical for:
    • Understanding client requirements
    • Building trust and confidence
    • Setting the foundation for the proposal
  • Agreement marks the official start of the project.