What is quality program?

Answer 1

Quality programs are tools that allow you to improve the Quality of your product.

There are two types of quality programs.

1. A Quality Process or Standard
2. Quality Assurance Software

Most reputable Software Quality Assurance Tools have at least some components of a quality system or standard.

You may have heard of a Bug Tracking System. This type of software is used to manage "bugs" that usually crop up during development and even after a software was released to the public. It helps you track bugs and assign the analysis and fixing to a development team member.

There's another more advanced type of quality software that is usually referred to as Issue or change management software. I've often heard it called a Program Support Log. It's usually more robust in terms of risk analysis and should include the ability to identify areas an Issue or Change can impact should it become an incident. For this reason, it's usually more proactive than a bug tracking system.

Here is a very broad definition of a Bug:

It is something technical in nature that is either not functioning or is functioning in an unexpected manner. Not everything that is identified as 'bug' will be a technical error. It could be an inquiry on a technical matter or a request for technical support. There are three types of bugs:

1. Support -- A request for technical help on a particular matter.
2. Error -- A technical problem.
3. Enhancement -- a request for a change in how something functions. This should trigger a Change Request in your organization.

A Program Support Log (Change or Issue management software) is much better at tracking and controlling unplanned events that can and in almost all cases do crop up. Things or events that can blindside you. The ability to discuss issues before they become incidents is also usually present in this type of software. There are 4 types of Incidents:

1. A Risk is something negative that may happen.
2. An Issue is something that has to be done but there is not a final decision on what to do.
3. A Change Request is seeking permission for a specific course of action which will change the project's schedule, cost or functionality.
4. A Discussion Item usually precedes a categorization of an Issue, Risk, or Change request.

I've worked in a few Software firms where they used Issue Management software to manage bugs only because it allows you to be more proactive, and brings more intelligence to the whole Quality Assurance process.