Quality management within the project will be a continuous process consisting of three steps subject to regular implementation:
- Quality planning
- Quality Assurance (QA)
- Quality control (QC)
Quality planning involves creating a quality management plan, following it, reviewing it periodically, and changing it as needed. The initial plan is defined in this document. Reference: “The project quality management plan“, https://www.yahowto.com/the-project-quality-management-plan/
Quality assurance determines the timing and quality control activities.
Quality control includes monitoring specific indicators subject to control and documenting the results thereof. Depending on the different moments of quality control, it includes different activities and parameters.
Control reports
Project quality control reports will support the objective of the quality management process.
They will contain information about the specifically established indicators of the monitored parameters at the relevant moments of quality control. Discovered discrepancies are described, risks are identified and adequate measures are initiated to avoid them.
The content of the control reports includes:
Overall assessment – within a few sentences, an overview of the quality of the project is made. In general: trouble-free, with minimal (acceptable) deviations, critical.
Indicators considered and the result achieved:
Acceptable result;
Conditionally acceptable result:
A necessary increase in the quality of the indicator;
Follow up on this;
Unacceptable or missing result:
Requirements must be met;
Follow-up required;
Identified risks;
Recommendations for the further course of the project;
Concerted quality improvement actions:
Actions – depending on the assessment of the quality of the project;
Participants – the parts of the project team they affect;
Other parties are required to be involved (eg the Board of Directors).
Quality management plan
The quality management plan is built on the decision that all quality control activities and efforts are concentrated at the end of each stage, as the last activities of the stage. Reference: “Quality documentation management”, https://bvop.org/learn/quality-documentation-management/
Completing a stage with a successfully conducted quality control ensures that the decisions made are correct and based on the necessary conditions that have been met. A review of indicators reflecting whether the necessary actions have been carried out, whether the necessary decisions have been made, and whether all requirements have been covered is carried out, and these indicators are specific to each stage and are described in the quality control. Further reading: “Quality management objectives in project execution“, https://securityinformationeventmanagement.com/quality-management-objectives-in-project-execution/
The objectives of the plan thus constructed are:
Quality assurance at project milestones;
Ensuring that all key activities are performed in compliance;
Enabling project managers to be constantly informed about the quality of the project.
The benefits of such a plan are:
Increasing the quality of the project;
Minimizing risks;
Managing customer expectations and satisfaction;
Increasing the transparency of the project;
Reduction of resource costs caused by rework;
Reducing the build-up of time delay
QA
Quality control activities are periodic and in the current project they will take place at key moments/dates during the project:
- After the start of the project
- After the Research stage ends
- After configuring the system
- After the end of the Implementation stage
- Before starting productive work
- After the completion of the project
Quality reviews are primarily aimed at verifying whether the results achieved meet the quality standards set in advance in the plan. The quality of the work products as a result of the project is not subject to reviews, since the relevant members of the business processes and functionalities team are responsible for them. Reference: “Quality management plan example template for a technology”, https://medfd.org/quality-management-plan-example-template/ (MEDFD.org)
Quality review programs are closely tied to the implementation methodology, but the specific content is adapted to the individual situation and objectives. The indicators and their permissible values from the point of view of quality assurance are presented in the next point of the document.
Perform quality control
Quality control after the Research stage
This point describes the necessary conditions and indicators that will be measured after the Study stage.
The necessary conditions for starting work on the activities for this quality control are:
Completed stage Preparation of the project
Built Deployment Concept and Migration Concept
Completed design of interfaces and functional extensions
Indicators considered
Metrics considered in this quality control:
Organizational structure (required)
Project participants and resources
Project team, roles, and responsibilities
Built, reviewed, and approved
Management plans (required)
Scope and change management and request log
Management of open questions and registry
Risk management and risk register
Created, reviewed, and approved
Project plan (required)
Linear project schedule
Drafted, reviewed, and approved Project Plan
Implementation concept (required)
Organizational structure
business processes
Additional developments
Data migration tools
User roles
Built, reviewed, and accepted Implementation Concept
Data Migration Concept (Required)
Scope of migration data
Required migration tools
Information carriers
Built, reviewed, and accepted Data Migration Concept
Technical infrastructure (required)
Infrastructure topology design
Built and installed development environment
Technically configured development environment
Quality control after system configuration
This point describes the necessary conditions and metrics that will be measured after the system is configured. Reference: “Applying control in project management”, https://60yearsnato.info/applying-control-in-project-management/
Prerequisites
The necessary conditions for starting work on the activities for this quality control are:
System configuration complete
Additional developments completed
Indicators considered
Metrics considered in this quality control:
Organizational structure (required)
Changes have occurred in the project team
Project team changes needed
Management plans (required)
Status of the change request log
Status of the open questions register
Risk register status
Project plan (required)
Adherence to the linear project schedule
Made adjustments to the line graph
Configure according to the Deployment Concept (required)
Performance and differences in organizational structure
Performance and differences in business processes
Performance and differences in additional developments
Performance and differences in data alignment tools
Performance and differences in user roles
Reasons for differences, approval, and implementation
Technical infrastructure (required)
Infrastructure topology changes
Installed development and test environment
Technically configured test environment
Testing Procedure (required)
Scope and types of tests
Test team, roles, and responsibilities
Schedule of the tests
Quality control after Implementation
This point describes the necessary conditions and indicators that will be measured after the Implementation stage. For QA and QC managers: “Quality control and quality assurance in Project Management and Agile practices”, https://scrumtime.org/quality-control-and-quality-assurance-project-management-agile-practices/
Prerequisites
The necessary conditions for starting work on the activities for this quality control are:
Integration test performed
Indicators considered
Metrics considered in this quality control:
Organizational structure (required)
Changes have occurred in the project team
Project team changes needed
Management plans (required)
Status of the change request log
Status of the open questions register
Risk register status
Project plan (required)
Adherence to the linear project schedule
Made adjustments to the line graph
Module tests (required)
Prepared test scenarios
Tests conducted with results
Issues are fixed or listed as open issues
Integration test (required)
Prepared test environment
Prepared test data
Prepared test scenarios
Tests conducted with results described
Issues are fixed or listed as open issues
Protocols (required)
Accepted protocol for conducted tests
Quality control before Production start
This point describes the necessary conditions and indicators that will be measured before the start of the Production Start of the system.
Prerequisites
The necessary conditions for starting work on the activities for this quality control are:
Conducted training
Finished product
Indicators considered
Metrics considered in this quality control:
Organizational structure (required)
Changes have occurred in the project team
Project team changes needed
Management plans (required)
Status of the change request log
Status of the open questions register
Risk register status
Project plan (required)
Adherence to the linear project schedule
Made adjustments to the line graph