Software Testing in Start ups
Startup Software companies often find themselves in a stage where inadequate test coverage and no proper product documentation puts them in a tight situation. These make it difficult for them to plan future releases as well as have a product reference in its totality.
Above all these often result in poor customer feedbacks and ultimately a loss in opportunities. What could be the probably reasoning for interesting product ideas to face these? Here are a few
1. Lack of a proper QA process
2. Lack of dedicated QA or test resources
3. Cost of testing not justified as a fulltime effort
4. Too involved in development that testing takes a back seat
5. Lack of product documentation and a structured approach t
6. No QA Architect in house to drive a QA Agenda
While all or some of the above pulls the strings to a spiral down, there are ways to mitigate it and before we see how, lets take a look at what entices Start ups to take action here
1. An awareness of the graveness of the issue
2. A Cost effective alternative that is not heavy on the budget
3. A Scalable Solution that can be ramped up fast
4. The part time availability of Architect level resources
5. Tools and Techniques that they don’t have to re-invent
6. A Plug and Play environment
7. No capital cost to kick start
Here are a few things that will define a right solution
1. Create a Budget for testing ($1000 upwards)
2. Go Offshore – Easily Manageable and cost effective
3. Get an exploratory testing done first so you can take stock of what you have
4. Do an Application profile to understand the product in its testable totality
5. Get Documentation support as part of the deal
6. Do part time and then full time engagements
7. A QA Architect’s part time involvement to define a process
8. Have extensive defect analysis and reporting
9. Start small and grow
Startup Software companies often find themselves in a stage where inadequate test coverage and no proper product documentation puts them in a tight situation. These make it difficult for them to plan future releases as well as have a product reference in its totality.
Above all these often result in poor customer feedbacks and ultimately a loss in opportunities. What could be the probable reasoning for interesting product ideas to face these challenges?
Here are a few
- Lack of a proper QA process
- Lack of dedicated QA or test resources
- Cost of testing not justified as a fulltime effort
- Too involved in development that testing takes a back seat
- Lack of product documentation and a structured approach to QA
- No QA Architect in house to drive a QA Agenda
While all or some of the above pull the strings for a spiral down, there are ways to mitigate it and before we see how, lets take a look at what entices Start ups to take action here
- Understanding the graveness of the issue
- A Cost effective alternative that is not heavy on the budget
- A Scalable Solution that can be ramped up fast
- The part time availability of Architect level resources
- Tools and Techniques that they don’t have to re-invent
- A Plug and Play environment
- No capital costs to kick start
Here are a few things that will define a right solution
- Create a Budget for testing ($1000 upwards)
- Go Offshore – Easily Manageable and cost effective
- Get an exploratory testing done first so you can take stock of what you have
- Do an Application profile to understand the product in its testable totality
- Get Documentation support as part of the deal
- Do part time and then full time engagements
- A QA Architect’s part time involvement to define a process
- Have extensive defect analysis and reporting
- Start small and grow
