Advanced Project Management Project Quality Management

1. Advanced Project ManagementProject Quality Management Ghazala Amin

2. Project Quality Management • Reference study materials • A guide to the Project Management Body of Knowledge (PMBOK Guide), Chapter 8 • Study notes • Dr. Kerzner’s book, Chapter 23

3. Project Quality Management (Slide Repeated) • The processes required to ensure that the project will satisfy the needs for which it was undertaken. • Modern quality management complements modern project management in that both recognize the importance of customer satisfaction and prevention over inspection. A company dedicated to quality usually provides training for all employees

4. Who is responsible for Quality?

5. Quality Leadership Reference: Dr. Harold Kerzner’s PROJECT MANAGEMENT A SYSTEMS APPROACH TO PLANNING, SCHEDULING, AND CONTROLLING Page 915: QUALITY LEADERSHIP

6. Principles of Quality Management Program at Sprint • Teamwork • Strategic Integration • Continuous Improvement • Respect for people • Customer Focus • Management by Fact • Structured Problem Solving

7. PMBOK Area: Quality Management Project Quality Management includes the processes for ensuring that the project satisfies the needs and requirements for which it was undertaken in the first place. Project Quality Management addresses both the project output (goal-focus) as well as the management of the project (process-focus). It recognizes the importance of customer satisfaction, prevention over inspection, management responsibility and continuous improvement. Processes covered under Project Quality Management are quality planning, quality assurance performance, and quality control.

8. Project Quality Management • Project Quality Management Processes (per PMBOK); • Quality Planning • Quality Assurance • Quality Control

9. Quality Planning • Quality planning involves identifying which quality standards are relevant to the project and determining how to satisfy them

10. Quality Planning • Quality planning involves identifying which quality standards are relevant to the project and documenting how the project will demonstrate compliance. • Quality planning should be performed regularly and in parallel with other project planning processes. For example: • The changes in the project product/service required to meet identified quality standards may require cost or schedule adjustments. • The desired product/service quality may require a detailed risk analysis of an identified risk source. • Quality should be planned in, not inspected in.

11. Quality Planning • Implies the ability to anticipate situations and prepare actions to bring about the desired outcome. • Important to prevent defects by: • Selecting proper materials. • Training and indoctrinating people in quality. • Planning a process that ensures the appropriate outcome.

12. Quality Policy • Quality Policy is the overall quality intentions and direction of an organization with regard to quality as formally expressed by top management. (ISO-8402) • Project management team is responsible for ensuring that the project stakeholders are fully aware of the quality policy. • Example – • “Providing best available health care facility to the patients at affordable price”. Medical facility’s quality policy.

13. Quality Management Plan • Quality Management Plan document sets out the specific quality practices, resources and sequence of activities relevant to a particular product, service, contract or project.(ISO-8402) • In ISO 9000 terminology, it should describe the project quality system: the organizational structure, responsibilities, procedures, processes, and resources needed to implement quality management. • Provides input to the overall project plan and must address quality control, quality assurance, and quality improvement for the project. • May be formal or informal, highly detailed or broadly framed, depending on the requirements of the project.

14. Quality Assurance • Quality assurance is the planned and systematic activities implemented within the quality system to provide confidence that the project will satisfy relevant quality standards

15. Quality Assurance • The process of evaluating overall project performance on a regular basis to provide confidence that the project will satisfy the relevant quality standards. • The organizational unit –”Quality Assurance” team that is assigned the responsibility for quality assurance. • Internal quality assurance: • assurance is provided to the project management team and to the management team of the performing organization. • External quality assurance: • assurance is provided to the customer and others not actively involved in the work of the project.

16. Quality Assurance • Quality assurance is the planned and systematic activities implemented within the quality system to provide confidence that the project will satisfy relevant quality standards • Project Manager can have greatest impact on the quality of his project by establishing process and procedures to assure that scope statement conforms to the actual requirement of the customer.

17. Quality Audit • The method most commonly employed for enforcing the Quality Assurance process is; • Quality audits • A structured review of all quality management activities. • The objective of a quality audit is to identify lessons learned that can improve performance of this project or of other projects within the performing organization. • May be scheduled or random; may be carried out by trained in-house auditors or by third parties such as quality system registration agencies.

18. Table 8-1. Table of Contents for a Quality Assurance Plan* • 1.0 Draft Quality Assurance Plan • 1.1 Introduction • 1.2 Purpose • 1.3 Policy Statement • 1.4 Scope • 2.0 Management • 2.1 Organizational Structure • 2.2 Roles and Responsibilities • 2.2.1 Technical Monitor/Senior Management • 2.2.2 Task Leader • 2.2.3 Quality Assurance Team • 2.2.4 Technical Staff • 3.0 Required Documentation • 4.0 Quality Assurance Procedures • 4.1 Walkthrough Procedure • 4.2 Review Process • 4.2.1 Review Procedures • 4.3 Audit Process • 4.3.1 Audit Procedures • 4.4 Evaluation Process • 4.5 Process Improvement • 5.0 Problem Reporting Procedures • 5.1 Noncompliance Reporting Procedures • 6.0 Quality Assurance Metrics • Appendix • Quality Assurance Checklist Forms *U.S. Department of Energy

19. Quality Control • Quality control involves monitoring specific project results to determine if they comply with relevant standards and identifying ways to eliminate causes of unsatisfactory results

20. Quality Control • Quality Control is the process of monitoring specific project results to determine if they comply with relevant quality standards • The organizational unit that is assigned responsibility for quality control.

21. Quality Control • Quality control involves monitoring specific project results to determine if they comply with relevant standards and identifying ways to eliminate causes of unsatisfactory results • Project Team members with specific technical expertise setup process and procedures to ensure each step of project provides quality output from design and development through implementation and maintenance.

22. Quality Assurance vs Quality Control Reference: Dr. Harold Kerzner’s PROJECT MANAGEMENT A SYSTEMS APPROACH TO PLANNING, SCHEDULING, AND CONTROLLING Page 988 and 989: QUALITY ASSURANCE AND QUALITY CONTROL

23. QA and QC Tools & Techniques

24. The Seven QC Tools Identification Analysis Cause and Effect Analysis Trend Analysis Histograms Data Tables Scatter Diagrams Pareto Analysis Control Charts

25. Data Table

26. Cause and Effect - Fishbone Chart Time Machine Method Material Energy Measure People Environ. Cause Effect Major Defect • Identify major and minor causes for the defect • Classify in related groups • Visualize the group with the most causes

27. Sample Fishbone or Ishikawa Diagram

28. Scatter Diagram Y X • Plot the results of two variables • Show trends • Show distribution around Central tendency • Highlight Exceptions (out of tolerance condition) • Source of data for the Pareto Chart

29. Pareto Analysis • Pareto analysis involves identifying the vital few contributors that account for the most quality problems in a system. • Also called the 80-20 rule, meaning that 80 percent of problems are often due to 20 percent of the causes. • Pareto diagrams are histograms, or column charts representing a frequency distribution, that help identify and prioritize problem areas.

30. Pareto Analysis - Definition • Pareto Diagram - A histogram ordered by frequency of occurrence that shows how many results were generated by each identified cause. • Pareto Law - A supposition that states that a relatively small number of causes will typically produce a large majority of the problems or defects. • Commonly referred to as the 80/20 principle in which 80% of the problems can be attributed to 20% of the causes.

31. Pareto Diagram Primary Purpose: Focus improvement efforts on the most important causes 15 10 5 0 Other Pressure Noise Wobble Pareto's rule: A large number of defects are the result of a small number of causes. Fix the problems that are causing the greatest number of defects first.

32. Sample Pareto Diagram Ranks defects in order of frequency of occurrence to depict 100% of the defects.

33. Statistical Sampling • Statistical sampling involves choosing part of a population of interest for inspection. • The size of a sample depends on how representative you want the sample to be. • Be sure to consult with an expert when using statistical analysis. • Example: QA team randomly selected 8 drawings from 80 engineering drawings generated during the planning and design phase for inspection. • This exercise of random selection is Statistical sampling.

34. Control Chart Number of defects - Process “A” 10 Upper Control 8 6 Upper Tolerance 4 2 0 -2 Lower Tolerance -4 -6 - -8 Lower Control -10 Time • Process results over time • Process is in control when the number of defects fall within upper and lower control limits. • Process adjustments are immediate corrective actions based on QC measure. • Process can be improved to meet tighter control limits: Processes in control should not be adjusted.

35. Sample Quality Control Chart

36. Quality Testing in IT World • Many IT professionals think of testing as a stage that comes near the end of IT product development. • Testing should be done during almost every phase of the IT product development life cycle.

37. Testing Tasks in the Software Development Life Cycle

38. Types of Tests • Unit testing tests each individual component (often a program) to ensure it is as defect-free as possible. • Integration testing occurs between unit and system testing to test functionally grouped components. • System testing tests the entire system as one entity. • User acceptance testing is an independent test performed by end users prior to accepting the delivered system.

39. Figure. Gantt Chart for Building Testing into a Systems Development Project Plan