QUALITY MANAGEMENT

The purpose for managing quality is to validate that the project deliverables are completed with an acceptable level of quality. Quality management assures the quality of the project deliverables and the quality of the processes used to manage and create the deliverables.
The key deliverables that need to meet quality standards are:

The Project Statement of Work
The Project Management Methodology

The key project process subject to project quality standards is the change management process used to manage change on the project.
A change is an alteration to the project scope, deliverables, or milestones that affect project cost, schedule, quality, or conformance of the deliverables to the agreed specifications. The Project Managers and Steering Committee will have overall responsibility for the change management process.

Changes may result in adjustment to the project completion schedule and the project costs. Should it be deemed necessary, IFCA reserves the right to reviewed and negotiate for these changes. The change will be processed once the mutually agreed upon and changes are defined and documented in a properly authorized Change Request Form. Test Users will document issues, questions and requests on a Software Incident Request (SIR) form. These SIR forms will be reviewed by the Implementer or Client Project Manager on a regular basis. SIRs may result in a Change Request being initiated.

Sign-off (Approval) will be obtained at the end of each phase of the project after Key Users have validated the document, prototypes or software. The project will not proceed until the sign-off has been obtained.

Phase 1 User discovers and reports problem.

Phase 2 Problem is reproduced and prioritized based on its severity and business impact.

Phase 3 Problem is assigned to development team for rectification by means of fixes, mitigations and workarounds. Once problem is rectified testing team will retest the rectified error.

Phase 4 Accumulate fixes and prepare patch release for distribution according to urgency and release policy.

Phase 5 Release patch to users is based on:
Every quarterly -- cumulative bug reports; or
Pre-determined number of problem reports received/urgency; or
Whichever comes first
Fixes for bugs with very low priority will be released in the following version.