1. Defects in Production
Finding critical defects, post deployment in a live environment, indicates that the testing carried out hasn’t tested the project requirements correctly. This results in your Operations (Ops) team spending a large portion of their time and budget resolving or working around the defects. Applying hot fixes to a live environment is a high-risk solution which can create further problems. The earlier testing is involved in the project, i.e. from the requirements phase, the earlier defects are found and the cheaper they are to fix.
2. Defects discovered by Customers
If you experience a spike in the number of Customer Service contacts post deployment this is usually as a result of new features not behaving as designed. This has a negative impact on revenue, brand and reputation and similar to point 1, puts pressure on your ops team, leaving your competitors product a more attractive option.
3. System Performance degrades after deployment
New features added to your system, or changes to the internal architecture can have a detrimental effect on system performance and the customers experience. To mitigate this risk, performance and load testing must be an integral part of your testing strategy.
4. Your testing Investment is below Industry average
According to the World Quality report 2016, companies spend 35% – 40% of development budgets on testing activities.
5. Project doesn’t pass quality gates.
We have all been in that meeting where the decision needs to be made – ‘go’ or ‘no go’. Tensions can be high and the business can be under severe pressure to release to market. This is no time to be delivering bad news to an unsuspecting group of stakeholders. The key to managing this situation is not to be in it in the first place. A well designed test strategy and reporting process will inform key stakeholders of testing progress and issues throughout the project and will avoid last minute surprises.
6. Do you know if your project is ready to go live?
Software will always have flaws. Testing is the only activity in the development process that proves:
- The system behaves the way it was designed (functional testing).
- The system performs to the desired KPI’s (performance testing).
- The system behaves the way the end user expects it to behave (UAT).
- The project delivers the overall businesses requirements.
A well designed Test Strategy will ensure that all of the effort in testing is focused on finding the critical business impacting defects.
7. Resourcing Issues
Good testers are worth their weight in gold. They can reduce development costs, time to market and improve product design. Building your own QA department with the broad spectrum of skills required to effectively plan and test your projects is expensive and time consuming. Celtic Testing can help overcome this obstacle. Our consultants have 20+ years’ experience delivering software projects, we can use our experience to help you deliver a high quality product to market, on time and with zero critical defects.
The above are some basic signs that you need to take a closer look at the role of ‘QA and Testing’ within your business. Call us to discuss your software quality challenges.