How much critical mass will the product/project/service need to allow for (software) testing?
Recently I participated in a local “coffee shop meet-up” along with photographers, coaches, entrepreneurs and start-ups. We could agree that coaches as well as testers give indirect value to the business – but while staff coaching could be individually sold to carpenters and hairdressers – (software) testing could not. Afterwards I challenged my self to think otherwise!
- Anyone know a business which isn’t a tech business these days?
- Anyone know a business which doesn’t have risks?
- Anyone know a business which doesn’t need information to guide decisions?
Good testing is an information and exploration activity – to find risks and present information to the stakeholders. Usually it’s easy to find the known risks to entrepreneurs – but good testing can test for unknown unknowns – even if there is no product or “just” a minimum viable product:
“The minimum viable product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort.” The definition’s use of the words maximum and minimum means it is decidedly not formulaic. It requires judgment to figure out, for any given context, what MVP makes sense.
Similarly minimum viable testing is an effort, that allows the team to collect tacit and explicit learning about the solution, given the context. Go look for it in your context – Testing can add business value to any project state