PROJECT QUALITY MANAGEMENT

PROJECT QUALITY MANAGEMENT

1. Plan Quality Management

   • This process identifying quality requirements and/or standards for the project and its deliverables
     • Inputs
       • Project charter
       • Project management plan
         • • Requirements management plan • Risk management plan • Stakeholder engagement plan • Scope baseline
       • Project documents
         • • Assumption log • Requirements documentation • Requirements traceability matrix • Risk register • Stakeholder register
       • Enterprise environmental factors
       • Organizational process assets
     • Tools & Techniques
       • Expert judgement
       • .Data gathering
         • Benchmarking
           • Involves comparing actual or planned project practices
         • Brainstorming
           • Used to gather data creatively from a group of team members to develop the quality management plan.
         • Interviews
       • Data analysis
         • Cost-benefit analysis
           • Is a financial analysis tool used to estimate the strengths and weaknesses of alternatives in order to determine the best alternative in terms of benefits provided
         • Cost of quality
           • Prevention costs.
             • Related to the prevention of poor quality in the products, deliverables, or services
           • Appraisal costs.
             • Related to evaluating, measuring, auditing, and testing the products, deliverables, or services
           • Failure costs (internal/external).
             • Related to nonconformance of the products, deliverables, or services to the needs or expectations of the stakeholders.
           • Reflects the appropriate balance for investing in the cost of prevention and appraisal to avoid failure costs.
       • Decision making
         • Multicriteria decision analysis
       • Data representation
         • Flowcharts
         • Logical data model
           • They are visual representation of an organization’s data, described in business language and independent of any specific technology.
         • Matrix diagrams
           • They show the strength of relationships between factors, causes, and objectives that exist between the rows and columns that form the matrix
         • Mind mapping
           • It may help in the rapid gathering of project quality requirements, constraints, dependencies, and relationships.
       • Test and inspection planning
       • Meetings
     • Outputs
       • Quality management plan
         • Is a component of the project management plan, is a component of the project management plan
       • Quality metrics
         • They describe a project or product attribute and how the control quality process will measure it
       • Project management plan updates
         • Risk management plan
         • Scope baseline
       • Project documents updates
         • Lessons learned register
           • Is updated with information on challenges encountered in the quality planning process.
         • Requirements traceability matrix
         • Risk register
           • New risks identified during this process are recorded in the risk register and managed using the risk management processes.
         • Stakeholder register
           • The additional information on existing or new stakeholders is recorded in the stakeholder register.

2. Manage Quality

   • The process of translating the quality management plan into executable quality activities .
   • Inputs
     • Project management plan
       • Defines the acceptable level of project and product quality
     • Project documents
       • Lessons learned register
         • Can be applied to later phases in the project to improve the efficiency and effectiveness of managing quality.
       • Quality control measurements
         • Used to analyze and evaluate the quality of the processes and deliverables of the project against the standards of the performing organization or the requirements specified
       • Quality metrics.
         • Uses these quality metrics as a basis for the development of test scenarios for the project and its deliverables and as a basis for improvement initiatives.
       • Risk report
         • Used to identify sources of overall project risk and the most important drivers of overall risk exposure
     • Organizational process assets
   • .Tools & Techniques
     • Data gathering
       • A checklist is a structured tool, used to verify that a set of required steps has been performed or to check if a list of requirements has been satisfied
     • .Data analysis
       • Alternatives analysis
         • Is used to evaluate identified options in order to select are most appropriate to use.
       • Document analysis
         • Focus on processes that may be out of control and may jeopardize meeting the specified requirements or stakeholders’ expectations.
       • Process analysis
         • Identifies opportunities for process improvementsand examines problems, constraints, and non-value-added activities that occur during a process.
       • Root cause analysis (RCA)
         • Used to determine the basic underlying reason that causes a variance, defect, or risk
     • Decision making
       • Project decisions can include choosing among different implementation scenarios or suppliers.
       • Product decisions can include evaluating the life cycle cost, schedule, stakeholder satisfaction, and risks associated with resolving product defects.
     • .Data representation
       • The information that represented in dofferents diagram : Affinity diagrams, Cause-and-effect diagrams, Flowcharts, Histograms, The matrix diagram, Scatter diagrams.
     • .Audits
       • Is a structured, independent process used to determine if project activities comply with organizational and project policies, processes, and procedures.
     • Design for X
       • Using the DfX may result in cost reduction, quality improvement, better performance, and customer satisfaction.
       • Is a set of technical guidelines that may be applied during the design of a product for the optimization of a specific aspect of the design.
     • Problem solving
       • The objetive is finding solutions for issues or challenges, also will help eliminate the problem and develop a long-lasting solution.
     • Quality improvement methods
       • Can occur based on findings and recommendations from quality control processes, Plan-do-check-act and Six Sigma are two of the most common quality improvement tools used to analyze and evaluate opportunities for improvement.
   • Outputs
     • Quality reports
       • Can be graphical, numerical, or qualitative, include all quality management issues escalated by the team; recommendations for process, project, and product improvements; corrective actions recommendations (including rework, defect/bugs repair, 100% inspection, and more); and the summary of findings from the Control Quality process.
     • Test and evaluation documents
       • Used to evaluate the achievement of quality objectives also include dedicated checklists and detailed requirements traceability matrices as part of the document.
     • Change requests
     • Project management plan updates
       • Quality management plan: The agreed-upon approach to managing quality may need to be modified due to the actual res
       • Scope baseline: May change as a result of specific quality management activities
       • Schedule baseline: May change as a result of specific quality management activities.
       • 4Cost baseline: May change as a result of specific quality management activities.
     • Project documents updates
       • 1. Issue log. 2. Lessons learned register 3. k Risk register.

3. Control Quality

   • The process of monitoring and recording the results of executing the quality management activities
   • Inputs
     • Project management plan
       • Defines how quality control will be performed within the project.
     • Project documents
       • essons learned register: be applied to later phases in the project to improve quality control.
       • Quality metrics: Describes a project or product attribute and how the Control Quality process will verify compliance to it.
       • Test and evaluation documents: are used to evaluate achievement of the quality objectives.
     • Approved change requests
     • Deliverables
       • Are outputs from the Direct and Manage Project Work process are inspected and compared to the acceptance criteria defined in the project scope statement.
     • Work performance data
     • Enterprise environmental factors
     • Organizational process assets
   • Tools & Techniques
     • Data gathering
       • Checklists. Described: help in managing the control quality activities in a structured manner.
       • Check sheets: are used to organize facts in a manner that will facilitate the effective collection of useful data about a potential quality problem.
       • Statistical sampling: involves choosing part of a population of interest for inspection , also is taken to measure controls and verify quality.
       • Questionnaires and Surveys: used to gather data about customer satisfaction after the deployment of the product or service
     • Data analysis
       • Performance reviews: measure, compare, and analyze the quality metrics defined by the Plan Quality Management process against the actual results.
       • Root cause analysis (RCA): used to identify the source of defects.
     • Inspection
       • Is the examination of a work product to determine if it conforms to documented standards
     • Testing/product evaluations
       • Is an organized and constructed investigation conducted to provide objective information about the quality of the product or service under test in accordance with the project requirements.
     • Data representation
       • Cause-and-effect diagrams: are used to identify the possible effects of quality defects and errors.
       • Control charts: are used to determine whether or not a process is stable or has predictable performance
       • Histograms.: can demonstrate the number of defects by source or by component.
       • Scatter diagrams: show the planned performance on one axis and the actual performance on the second axis.
     • Meetings
       • Approved change requests review: should also check that partial changes are completed and all parts have been properly implemented, tested, completed, and certified.
       • Retrospectives/lesson learned: to discuss: Successful elements in the project/phase, What could be improved, What to incorporate in the ongoing project and what in future projects, and What to add to the organization process assets.
   • Outputs
     • Quality control measurements
       • Are the documented results of Control Quality activities
     • .Verified deliverables
     • Work performance information
       • includes information on project requirements fulfillment, causes for rejections, rework required, recommendations for corrective actions, lists of verified deliverables, status of the quality metrics, and the need for process adjustments
     • Change requests
       • Are processed for review and disposition through the Perform Integrated Change Control proces
     • Project management plan updates
     • Project documents updates
       • . Issue log.: a deliverable that does not meet the quality requirements is documented as an issue.
       • Lessons learned register: is updated with information on the source of quality defects and how they could have been avoided
       • Risk register: New risks identified during this process are recorded in the risk register and managed using the risk management processes.
       • Test and evaluation documents: may be modified as a result of this process in order to make future tests more effective.

Images and files in the map