Presentation on theme: "Process and Product Quality Assurance (PPQA)"— Presentation transcript:
1Process and Product Quality Assurance (PPQA) Intermediate Concepts of CMMIPresentation AssignmentNicolae Giurescu
2Importance of PPQAProvides objective insight into processes and associated work products.Visibility into project’s processes.Objective evaluations.Independent group.Defined criteria.Identifying, documenting and resolving noncompliance issues.Process without adequate control is just good documentation.
3Benefits of PPQASupports delivery of high-quality products and services.Provides feedback on project’s processes implementation.Identifies opportunities for process improvement.Identifies “dead” processes, that exists only in the process documentation.By improving the quality of process, waste and rework are drastically reduced or even eliminated.A system that continually improves relies on feedback. A reactive system fixes problems in response to feedback, while an improving system fixes the process in response to feedback.
4PPQA Depends on … Project Planning Verification For identifying processes and associated work products that will be objectively evaluated.VerificationFor more information about satisfying specified requirements.Peer reviewsInspectionsTests, …
5PAs that Depend on PPQA ALL the rest. For objective feedback into processes and associated work products and services, regarding their conformance to applicable process descriptions, standards and procedures.For ensuring that the noncompliance issues are addressed.
6Ordering of SPs in PPQASG 1 Objectively Evaluate Processes and Work Products.SP 1.1 Objectively Evaluate Processes.SP 1.2 Objectively Evaluate Work Products and Services.SG 2 Provide Objective Insight.SP 2.1 Communicate and Ensure Resolution of Noncompliance Issues.SP 2.2 Establish Records.Note: Can be concurrent and repetitive.
7“Critical” SPs in PPQA - 1 In communicating the noncompliance issuesit is important to focus on data, not cause,and never on assigning blame.SP Communicate and Ensure Resolution of Noncompliance Issues.Sub practice 1, Resolve each noncompliance with the appropriate members of the staff where possible.Sub practice 2, Escalate noncompliance issues that cannot be resolved within the project to the appropriate level of management designed to receive and act on noncompliance issues.
8“Critical” SPs in PPQA - 2 Records of PPQA activities are primesources for process improvement andlessons learned.SP Establish records.Sub practice 1, Record process and product quality assurance activities in sufficient detail such that status and results are known.Sub practice 2, Revise the status and history of the quality assurance activities as necessary.
9Generic Practices and PPQA GPs with special significance:GP 2.2 Plan the ProcessGP 2.3 Provide ResourcesGP 2.4 Assign ResponsibilityGP 2.5 Train the PeopleGP 2.7 Identify and Involve Relevant StakeholdersGP 2.10 Review Status with Higher Management!!! PPQA implements GP 2.9 Objectively Evaluate Adherence, for all other PAs
11QA Actions vs. Project Expectations - 1 Coaching and support for the R&D process institutionalization and milestones preparation (inputs, objectives, outputs).Document reviewing and dedicated processes structuring reviewing activitiesSystem Design SpecificationsRequirements TraceabilitySoftware Test Plan, …
12QA Actions vs. Project Expectations - 2 Quality Assurance PlanDefinition / Customization of specific project’s processes:Defect trackingProject trackingDesign changeRisk managementList of QA tasks planned for the projectNoncompliance management
16Broken Traceability Matrix Problem: X % of bad links from requirements to design in subsequent documentation baselinesQuick fix: verify all and correct bad linksRoot causes:Links to old versionsLack of time to properly update the traceabilitySolutionMigrate from Word to DOORSStore in the same database all engineering specs
17“Forgotten” Requirement Changes Problem: X% of requirement changes not reflected into the design and test casesQuick fix:Rework if possibleReport the change to future versionsRoot causes:Changes not communicatedChanges occurred to late to be consideredSolution:Automatic notificationJoint requirement reviews
18Unmanaged Defect Reports Problem: defects discovered during the development phase were solved in an ad-hoc wayQuick fix: none consideredRoot causes:No system to manage defects during developmentSolution:Start managing defects during development, same way as during maintenance
19Being Late Problem: X% of missed schedule milestones Quick fix: Revised scheduleRoot causes:Imposed schedule milestonesEver changing WBSWrong task estimationsInsufficient resourcesSolution:Incremental integration and development plan
2050% of issues are related to process problems that have been corrected