Why Quality is Everyone’s Responsibility & How to Improve It

Testing and Quality Assurance

It is often assumed that testing alone is adequate to conduct quality assurance. However, sufficient testing alone is not enough to assure quality, as testing could be performed correctly yet still fail once the test pack has been executed. Below, the correct parameters of both testing and quality assurance, as well as how QA is properly conducted when creating software, will be explored. 

Testers Are Information Providers

In and of itself, QAs, or testers, cannot fix any problems regarding the software. Yet, testing does provide the following information that is crucial to software development:

• Accurately relay the status of a given solution at a given stage of development
• Provide development with target areas to focus their efforts
• Let the business know if the project is on track, or not
• Let training get their ducks in a row ahead of the roll-out

With the right tools, correct coverage, appropriate test conditions, efficient prioritization, and robust strategy, one can easily attain the correct information needed from testers. However, it is also crucial that you acquire good test reporting. 

How to Improve Software Quality with Simple Information

With good testing in place, you can provide valuable information to the whole project. What the project does with that information is the key to achieving high-quality solutions. Other teams should work closely with the testers to understand the information and what to do with it. 

Here are 3 specific teams, and how they can drive software quality by utilizing simple test information:

1. How Your Delivery Team Can Use Test Data

Defect Reports are key to helping your delivery team drive quality. But it’s not just having the reports, it’s how you use them – and that’s in Defect Triage. Teams should not simply leave other teams out of the loop by not providing Defect Reports, as this is a fundamental breakdown in communication and quality will undoubtedly suffer.

Working through Defect reports together allows for effective triage.

It brings together tests and delivery. Effective triage cuts right to the facts:

• Where are your high-defect areas/functionality?
• What are your recurring issues?
• Where does delivery need extra/less focus?

1. How Your Delivery Team Can Use Test Data

Defect Reports are key to helping your delivery team drive quality. But it’s not just having the reports, it’s how you use them – and that’s in Defect Triage.

How many times have you seen the siloed approach to delivery/test? – The classic ‘throw it over the fence’ and let the other team deal with it.

This approach is never going to get anywhere. It’s a fundamental breakdown in communication and quality will undoubtedly suffer.

You just can’t expect the other parties to know the subtleties of the defects, understand the patterns or appreciate the differences.

Working through Defect reports together allows for effective triage.

It brings together tests and delivery. Effective triage gets rid of the need to play the telephone game and cuts right to the facts:

• Where are your high-defect areas/functionality?
• What are your recurring issues?
• Where does delivery need extra/less focus?

2. How Project Management Can Use Test Data

Project management cannot remain rigid when it comes to specific outcomes that they desire for a project. If the execution does not occur in the way they plan, expectations must be adjusted accordingly. This is why having the correct information regarding the project is imperative if it is to be completed successfully. 

The best place to get project information is the test team.

The right test progress charts will quickly highlight areas of concern. It’s not filtered through team leads or development. Progress charts are so simple, but they give management great insight and control. Project management can use that control to:

• Adjust resources or alter release dates.
• Set realistic expectations with the project stakeholders.
• Pull the plug before costs and durations spiral out of control.

3. How Training Can Use Test Data

High-Quality software requires effective training material. Unfortunately for the training team, they’re often the last thought of any team member during a project. Training time is squeezed as much as tests, but they’re often shut out of the project communications. Never mind the challenge of working with end-users at various levels of experience and proficiency.

You must keep training informed on test progress in the following ways:

• Understand which areas are complete and ready to be documented
• Avoid developing redundant material for broken functionality
• Line up training courses at the right times – after test/before go-live

Why Quality is Everyone's Responsibility

Testers alone can’t assure quality, but good testing can highlight low-quality.

Through their various reports, testers provide the rest of your project with the information needed to drive a quality solution:

• The whole project can understand the status of your given solution at any time
• Delivery can focus their efforts
• Management can steer the project
• Training can create and deliver material effectively

Testers are information providers – they’re not the enemy.

Teams should utilize their reports, make the most of their information and let the whole project drive software quality.