Project Quality Management PDF

Project Quality Management. 1  Session objectives Explain quality and project quality management Explain project quality management processes Describe tools and techniques Explain types of project quality costs...

Project Quality Management. 1  Session objectives Explain quality and project quality management Explain project quality management processes Describe tools and techniques Explain types of project quality costs 2  What is Quality?  ISO defines quality as the totality of characteristics of an entity that bear on its ability to satisfy stated or implied needs.  Or quality is simply what the customer or stakeholder needs from project deliverables/output.  Other experts define quality based on: ◦ Conformance to requirements: meeting written specifications/task completeness. ◦ Fitness for use: ensuring a product can be used as it was intended.3 Cont’d Conformance to requirements: meeting written specifications/task completeness. For example, if the project scope statement requires delivery of 100 computers with specific processors and memory, you could easily check whether suitable computers had been delivered. 4 Cont’d Fitness for use: ensuring a product can be used as it was intended. For example, If these computers were delivered without monitors or keyboards and were left in boxes on the customer’s shipping dock, the customer might not be satisfied because the computers would not be fit for use. 5  Project Quality Management The process of frequently measuring the quality of all activities and taking corrective action until the team achieves the desired quality. It includes the processes for incorporating the organization’s quality policy regarding:  Planning, managing, and  Controlling project/product quality requirements in order to meet stakeholders objectives. 6  Project Quality Management The purpose of project quality management is to ensure that the project will satisfy the needs for which it was undertaken. Recall that project management involves meeting or exceeding stakeholder needs and expectations. 7  Project Quality Management If a project’s stakeholders are not satisfied with the quality of the project management or the resulting products of the project, the project team will need to adjust scope, time, and cost to satisfy the stakeholder. Meeting only written requirements for scope, time, and cost is not sufficient. To achieve stakeholder satisfaction, the project team must develop a good working relationship with all stakeholders and understand their stated or implied needs. 8  Modern Quality Management Requires customer satisfaction (tackle problems in real-time). Prefers prevention over inspection. Recognizes management responsibility for quality. Establish and determine steps to achieve standards Control cost of a project (tackle problems before they cut into your budget). 9  Project Quality Management Processes Quality planning: identifying which quality standards are relevant to the project and how to satisfy them. Quality assurance: evaluating overall project performance to ensure the project will satisfy the relevant quality standards. Quality control: monitoring /checking specific project results to ensure that they obey with the relevant quality standards and identifying ways to improve overall quality.  It is all about identifying solutions to problems relating to quality. 10  Quality Planning  The process of identifying which quality standards are relevant to the project and how to satisfy them.  In this process, identify the quality requirements for your project deliverables and how the project needs to be managed; how this process will be documented and how that information will be delivered (meetings, emails, etc) and include metrics for measuring quality(a quality checklist). 11  Cont’d…  A quality management plan is :  A document that helps project management teams to maintain quality standards throughout the execution and completion of a project.  Or describe how you plan, to conduct various quality processes on your project. 12 Cont’d Several tools and techniques are available for planning quality management. For example, design of experiments is a technique that helps identify which variables have the most influence on the overall outcome of a process. Understanding which variables affect outcome is a very important part of quality planning. For instance, computer chip designers might want to determine which combination of materials and equipment will produce the most reliable chips at a reasonable cost. 13  Cont’d In quality planning for projects, it is important to describe key factors that directly contribute to meeting the customer’s requirements. Organizational policies related to quality, the particular project’s scope statement and product descriptions, and related standards and regulations are all important input to the quality planning process. Important aspects of IT projects that affect quality include functionality and features, system outputs, performance, and reliability and maintainability. 14 Cont’d Functionality is the degree to which a system performs its intended function. Features are the system’s special characteristics that appeal to users. It is important to clarify what functions and features the system must perform, and what functions and features are optional. 15  Cont’d Performance addresses how well a product or service performs the customer’s intended use. To design a system with high-quality performance, project stakeholders must address many issues. Reliability is the ability of a product or service to perform as expected under normal conditions. Maintainability addresses the ease of performing maintenance on a product. Or Enabling ease of future updates and repairs. 16  Quality Assurance(QA) It is one thing to develop a plan for ensuring the quality of a project. it is another to ensure delivery of high-quality products and services. The term quality assurance is often used to describe the activities related to satisfying the relevant quality standards for a project. 17  Quality Assurance(QA) Quality assurance is the process, that includes all the activities related to satisfying the relevant quality standards for a project. or a process of translating quality mang plan in to executable quality activities that incorporate the organizations quality policies in to the project. The goal of quality assurance is continuous quality improvement. 18  Quality Assurance(QA) An important tool for managing quality is a quality audit. Important inputs for performing quality assurance are the quality management plan, process improvement plan, quality metrics, quality control measurements, and project documents. 19  Key Activities of Quality Assurance(QA) It involves evaluating the project’s processes and overall performance to ensure they align with the established quality standards. Key Activities: Process Audits: Regularly review project processes to ensure compliance with the quality management plan. Process Improvement: Identify areas of inefficiency or inconsistency in processes and implement enhancements. Training: Equip team members with the skills and knowledge required to maintain quality standards. 20  Quality Control(QC)  The process of monitoring and recording specific project results to ensure that,  They obey with the relevant quality standards  The project outputs are complete ,correct and meet customer expectation.  It is similar to QA, but QA focuses on improving processes to maintain quality standards and prevent issues, while quality control focuses on inspecting and identifying issues. 21  Cont’d…  The main outputs of this process are acceptance decisions, rework , process adjustments.  Acceptance decisions determine if the products or services produced as part of the project will be accepted or rejected.  Rework is action taken to bring rejected items into compliance with product requirements, specifications, or other stakeholder expectations.  Rework often results in requested changes and validated defect repair, and it results from recommended defect repair or corrective or preventive actions 22  Quality control It focuses on monitoring specific project results to ensure they meet the relevant quality standards. It is a reactive process aimed at identifying and addressing defects or variances. Key Activities: Inspection: Examine deliverables to verify compliance with quality requirements. Testing: Use various methods (e.g., software testing, stress testing) to evaluate functionality and reliability. Defect Identification and Correction: Log, categorize, and fix defects in deliverables. 23  Key Differences: QA and QC Quality Control Aspect Quality Assurance (QA) (QC) Focus Process improvement Product inspection Objective Identify and fix Prevent defects defects Timing At the end of Throughout the lifecycle phases/deliverables Responsibility Ensuring proper Ensuring defect-free processes outputs 24  Tools and Techniques For Quality Contro  Some of tools and techniques include  Pareto analysis  Testing  Statistical sampling  Quality control charts By utilizing these tools and techniques, project managers can effectively maintain and improve the quality of deliverables while ensuring alignment with project objectives. 25  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% of problems are often due to 20% of the causes. Pareto diagrams are histograms that help to identify and prioritize problem areas. 26  Sample Pareto Diagram A Pareto chart is used to rank problems or defects in order of importance. 27  Testing The process of evaluating a product, service, or process to ensure it meets specified quality standards. Application: Includes functional testing, performance testing, stress testing, and user acceptance testing. Verifies whether the product works as intended and meets customer expectations. 28  Testing Benefits: Reduces the likelihood of defects reaching the customer. Enhances customer satisfaction and confidence in the product or service. Many SW professionals think testing as a stage that comes near the end of SW product development. Testing should be done during almost every phase of the SDLC. Can be manual or automated. 29 Testing tasks in the software development life cycle 30  Types of Tests A unit test is done to test each individual component (often a program) to ensure it is as defect free as possible or not. Integration testing occurs between unit and system testing to test functionally grouped components. It’s Purpose is to test the interaction between integrated components to ensure they work together seamlessly. System testing tests the entire system as one entity. User acceptance testing is an independent test performed by the end user prior to accepting the delivered system. 31 Gantt Chart for Building Testing into a Systems Development Project Plan 32  Statistical Sampling and Quality control charts  Reading assignment……. 33  Improving Software Project Quality A large percentage of quality problems are associated with management, not technical issues. Several suggestions for improving quality for software projects include: Leadership that promotes quality Understanding the cost of quality. Focusing on organizational influences and workplace factors that affect quality. Following maturity models to improve quality 34  Cost of Quality(COQ) COQ is money spent dealing with issues during and after the project, to fix any failures. It can be: Cost of conformance (preventive cost) or delivering products that meet requirements : related to training, documentation process, the equipment needed, and testing or inspections and fitness for use. Cost of nonconformance (internal failure costs) or taking responsibility for failures or not meeting quality expectations: 35 These consist of reworking something or scrapping it entirely.  Cost Categories Related to Quality  The Cost of Quality category codes are the following: Prevention Costs Appraisal Costs Internal Error Costs External Error Costs Measurement and test equipment costs 36  Prevention Costs Prevention costs are investments made ahead of time in an effort to ensure conformance to requirements. Costs incurred to prevent defects or errors from occurring in the first place. Examples include activities such as orientation of team members, training, and the development of project standards and procedures. 37  Appraisal Costs Appraisal costs are costs incurred to identify defects after the fact. Costs associated with measuring, evaluating, and inspecting products or services to ensure they conform to quality standards. Examples include activities such as walkthroughs and testing. 38  Internal Error Costs Costs that arise when defects or errors are identified before the product or service is delivered to the customer. Internal error costs are the costs of rework and repair before delivery to a customer. An example is fixing faults detected during internal testing. 39  External Error Costs External error costs are the costs of rework and repair after delivery to a customer. One example would be rework and repair resulting from acceptance testing. Another example would be the actual costs incurred during warranty support/ license. 40  Measurement and test equipment costs: Measurement and test equipment costs: capital cost of equipment used to perform prevention and appraisal activities. 41  ISO 9000 An international set of standards for quality management. Applicable to a range of organizations from manufacturing to service industries. ISO 9001 applicable to organizations which design, develop and maintain products. ISO 9001 is a generic model of the quality process that must be instantiated for each organization using the standard. 42 Software quality attributes Safety Understandability Portability Security Testability Usability Reliability Adaptability Reusability Resilience Modularity Effi ciency Robustness Complexity Learnability 43. Many thanks 44