4squareviews

This post discusses the outputs of the Manage Quality process, which focuses on quality assurance, that is, making sure that the quality-related processes on the project are done correctly, as opposed to the Control Quality process, which makes sure that the results of the project are done correctly.

8.2.3 Manage Quality Outputs

8.2.3.1 Quality Reports

The information contained in the quality reports is to used by the project team in order to take corrective actions, either to the processes themselves or to the product.  The information may include the following:

• Quality management issues escalated by the project team
• Recommendations for improvements to the processes of the project or to the product itself to reduce the probability of potential defects (preventive actions)
• Recommendations for corrective actions to detect defects (inspection, testing, etc.) or to repair defects before they go to the customer (rework/scrap).
• Summary of findings from the Control Quality process.

These quality reports are then distributed to all stakeholders who are interested in quality and/or those who have influence on quality.

8.2.3.2 Test and Evaluation Documents

These are the documents which are to be used in the next process 8.3 Control Quality.  They may include:

• Checklists (to make sure that all processes are done correctly)
• Check sheets (to document any results that are nonconforming to the quality standards)
• Requirements traceability matrices (to trace quality metrics to the specific requirements they measure)

8.2.3.3 Change Requests

As a result of this process, there may be recommendations for changes to the following:

• Project management plan (particularly the quality management plan or any of the baselines for scope, schedule, and cost–see paragraph 8.2.3.4 below)
• Project documents (particularly the issue log, lessons learned register, or the risk register–see paragraph 8.2.3.5 below)
• Project or product management processes (as a result of quality improvement activities)

These are then made inputs to process 4.6 Perform Integrated Change Control.

8.2.3.4 Project Management Plan Updates

• Quality management plan–sometimes rather than conforming the results to the plan, you may find that the plan was unrealistic, in which case you may need to modified the agreed-upon approach to managing quality based on the actual results.
• Scope baseline–specific quality management activities may change the deliverables (found in the project scope statement) or to the work packages (found in the WBS)
• Schedule baseline–specific quality management activities may impact the schedule, in which case the schedule baseline may need to be changed
• Cost baseline–specific quality management activities may impact the budget, in which case the cost baseline may need to be changed.

8.2.3.5 Project Documents Updates

• Issue log–as a result of the audits done as part of the quality assurance process, new issues may be raised which are recorded in the issue log.
• Lessons learned register–information is added to the register on
  • challenges encountered during this quality management process and how they could have been avoided or
  • approaches that worked well for managing quality
• Risk register–information on new risks identified during this process are recorded in the risk register to be managed using the risk management processes (covered in chapter 11)

The next post covers the inputs to the next process 8.3 Control Quality.

Filed under: Uncategorized |