Leave feedback
  • Featured

    Working with Quality Management

Write an Article
Friday 04 December, 2009
Johan Magne Johan Magne
0 likes 7523 views

The project quality management includes the processes required to ensure that the project meets the requirements defined for the project. Processes listed in this article will interact and overlap in project phases; output from quality planning is important as input for both quality assurance as well as for quality control.

The project quality planning directs the project management, the quality assurance directs the process and the quality control the product. An overview of the project quality environment for the StreamServe implementation project is as illustrated below:


Overall ownership of the quality management domain is a project management responsibility. In the same way, the ownership for project quality assurance is a QA team responsibility (typically consisting of StreamServe project manager and lead developer); the ownership of the project quality control is a responsibility of product developers. Project quality audits are typically carried out by StreamServe PMO or StreamServe solution architects external to the project. Such quality audits should focus on overall processes and all aspects of project status - basically provide an up to date health check.

The main difference between project quality assurance and control is that the quality assurance focuses on project management life cycle phases and activities whereas the quality control focuses on product development life cycle phases and activities.

The data flow overview of project quality management is as follows:


Project Quality Planning

On a corporate level the quality policy is set, which affects the quality process on a sub-organization level, where a typical StreamServe project is planned and executed. The division’s quality process then sets the guideline for the StreamServe project.

Typically, project quality planning for a StreamServe implementation project involves identifying the project quality expectations relevant to the project and determining how to satisfy them. This process should be carried out in parallel to other project planning activities. 

During the project planning phase, a list of project and product acceptance criteria should be listed and included in the project quality management plan. In addition to this, constraints and product-relevant items should be documented for the project and hence customizing the project quality plan for the StreamServe implementation. The product acceptance criteria should capture the quality attributes of the project, process and product. All roles and responsibilities for the quality management activities also need to be established and included in the project quality plan.

Project Quality Assurance

The quality assurance process should answer the question how the project should be carried out. The PMI definition of quality assurance is “the process of auditing the quality requirements and the results from quality control measurements to ensure appropriate quality standards and operational definitions are used.” (PMBOK, 4th edition). 

For a StreamServe implementation, as is the case for IT system implementations in general, the relative cost/time to fix a fault of the project delivery increases along with time of the project. In the requirements and functional design phase, the cost is relatively smaller than if detected in acceptance testing. This opportunity should lead the strategy for the quality assurance strategy.

It is up to the project manager to decide on the best practice when carrying out the project, however typically the project and the QA team decide on a number of gates or checkpoints that should match project characteristics and quality requirements in order to meet the agreed exit criteria. A recommended practise is to use a checklist for this process. 

Project Quality Control

The quality control process should verify that the development is heading in the right direction and is usually performed by the StreamServe developer(s). The PMI definition of the quality control is “the process of monitoring and recording results of executing the quality activities to assess performance and recommended necessary changes”.  

Project quality control can be carried out by anyone in the project, apart from the person who has defined the control process. Needed in order to carry out project quality control is knowledge about a) the project, and, b) the project requirement specifications.

For a StreamServe implementation project, quality control is typically carried out with development tests for each project item and control is continuously increased along with project time schedule incorporating more project components integrating with surrounding and depending systems.


Tools & Techniques

To summarize the project quality management process, a quality management plan should be defined during the planning phase, which is then used as input for quality assurance and control.

Typical tools for the quality control of a StreamServe implementation project are data gathering tools (rather than also common data analysis tools). Data-gathering tools includes verification techniques (truth, correct or not), validation techniques (value, correct or not) and checklists and check sheets. The typical process is for verification to be done early in the project and the validation later, when there is for instance a need to assure the correctness of the solution or a need to pinpoint the source of a defect.

An overview of the process and the input and output for the areas within the project quality management environment is as follows. Output from one domain serves as input for the next and it is recommended that tools and techniques used in the StreamServe implementation project are customized in order to reflect this process described below.  


Comments (1)

  • hi,

    Thanks for information ,can u share (excel or doc) ,quality management plan & quality audits




    Friday 03 February, 2012 by Anchal khare


Post comment