QUALITY MANAGEMENT PLAN

Transcription

1 Last updated: 10/30/09 Revision Number: V3 QUALITY MANAGEMENT PLAN 1 INTRODUCTION 1.1 PURPOSE OF THE PROJECT QUALITY MANAGEMENT PLAN The Project Quality Management Plan documents the necessary information required to effectively manage project quality from project planning to delivery. It defines a project s quality policies, procedures, criteria for and areas of application, and roles, responsibilities and authorities. The Project Quality Management Plan is created during the Planning Phase of the project. Its intended audience is the project manager, project team, project sponsor and any senior leaders whose support is needed to carry out the plan. 2 PROJECT QUALITY MANAGEMENT OVERVIEW 2.1 ORGANIZATION, RESPONSIBILITIES, AND INTERFACES Name Role Quality Responsibility Ron Schaefer Project Manager Quality mentoring & coaching Genaya Culver Development Team Lead Quality audits Al Veile Functional Analyst Functional audits Al Hovde Systems Analyst System audits Dan Stock Economic Analyst Performance measurement 2.2 TOOLS, ENVIRONMENT, AND INTERFACES Tool WBS Description C-TIP Performance Measurement Planning) WDU Performance Measurement Planning Unit Testing Assurance) CTIP 4.6 WDU 4.6 CTIP (IMEX 1) CTIP (IMEX 2) CTIP (CUT) CTIP (RTTM) CTIP (DRG) WDU 3.1.6, 3.2.7, (WDU) Includes definition of performance metrics, development and execution of C-TIP cost-benefit analyses, and reports on test findings and lessons learned from the C-TIP deployment test Planning = definition/measurement) Includes definition of performance metrics, development and execution of WDU cost-benefit analyses, and reports on test findings and lessons learned from the WDU deployment test Planning = definition/measurement) Unit Testing is the lowest level of software testing. It is used to test the logic and inputs and outputs of units (Analyzing and improving quality, i.e., performing Quality Assurance, WBS 4.1) Page 1 of 6

2 Integration Testing Assurance) System Testing Assurance Alpha/Beta Testing Assurance Issue Log/Pareto Analysis Control) CTIP (IMEX 1) CTIP (IMEX 2) CTIP (CUT) CTIP (RTTM) CTIP (DRG) WDU 4.1.1, (WDU)) CTIP (IMEX 1) CTIP (IMEX 2) CTIP (CUT) CTIP (RTTM) CTIP (DRG) WDU (WDU) CTIP (IMEX 1) CTIP (IMEX 2) CTIP (CUT) CTIP (RTTM) CTIP (DRG) WDU (WDU) CTIP WDU Integration Testing includes documenting the test procedures for each C-TIP application and the problem resolution for each issue identified during the testing (Analyzing and improving quality, i.e., performing Quality Assurance, WBS 4.1) This is the highest level of testing. It is used to ensure the software meets the requirements of the system. In our case, the use cases and nonfunctional requirements define the requirements of the system. (Analyzing and improving quality, i.e., performing Quality Assurance, WBS 4.1) Alpha testing is normally used to test partial functionality of a system to get early feedback on how well it performs its functions. Beta testing - this testing is usually performed by users and is the last test prior to releasing the software for general use. (Analyzing and improving quality, i.e., performing Quality Assurance, WBS 4.1) The issue log will document all problems encountered with C-TIP and WDU during the deployment test period, and the steps taken to resolve the problem. Logging and categorizing the issues facilitates Pareto Analysis, which can show how many problems of each type/category/cause were generated during the deployment test Control monitoring and controlling actions) 3 PROJECT QUALITY MANAGEMENT At the highest of levels Quality Management involves planning, doing, checking, and acting to improve project quality standards. PMI PMBOK breaks the practice of Quality Management into three process groups: Quality Planning (QP), Quality Assurance (QA) and Quality Control (QC). The following sections define how this project will apply each of these practice groups to define, monitor and control quality standards. 3.1 QUALITY PLANNING THE C-TIP PROJECT TEAM IS PLANNING TO DEFINE PERFORMANCE METRICS, CONDUCT A COST-BENEFIT ANALYSIS, AND DOCUMENT TEST FINDINGS AND LESSONS LEARNED. THE SPECIFIC METRICS, COST-BENEFIT STRUCTURE, AND TEST PROCEDURES/FINDINGS HAVE NOT BEEN DOCUMENTED YET, BUT HAVE BEEN ACCOUNTED FOR IN THE SCHEDULE. SEE WBS Define Project Quality [Identify quality standards and expectations for customers, the project, organization and federal regulations, define customer and project goals, quality Page 2 of 6

3 standards, critical success factors, and metrics for which to measure success, and outline acceptance criteria for project deliverables and product performance.] Measure Project Quality [Identify desired metrics and related monitoring processes for which to measure quality standard, develop a plan for measuring quality, define methods of data collection and archiving, and document timeframe for measurement and metrics reporting.] 3.2 QUALITY ASSURANCE QUALITY ASSURANCE IS CURRENTLY DOCUMENTED BY A BLANKET WBS TASK, 4.0. THE C-TIP PROJECT TEAM IS PLANNING FOR MOST OF THE SOFTWARE TESTING PROCEDURES TO ACCOUNT FOR THE EXECUTION/PERFORMANCE OF QUALITY ASSURANCE, TO INCLUDE: CODE AND UNIT TESTING, INTEGRATION TESTING, SYSTEM TESTING, AND ALPHA/BETA TESTING. THESE TESTS HAVE BEEN ACCOUNTED FOR UNDER THE SCHEDULE FOR EACH C-TIP APPLICATION, ALTHOUGH SPECIFIC TEST PROCEDURES AND LOGS HAVE NOT BEEN DEVELOPED YET. TEST PROCEDURES AND TEST REPORTS WILL BE WRITTEN FOR INTEGRATION TESTING AND SYSTEM TESTING. UNIT TESTS WILL BE DONE USING SOFTWARE TOOLS. SPECIFIC WBS ITEMS ARE LISTED IN THE TABLE ABOVE Analyze Project Quality [Analyze quality data, document opportunities for improvement and apply what was learned from quality analysis to eliminate gaps between current and desired levels of performance.] Improve Project Quality [Identify ways of doing things better, cheaper, and/or faster. For projects, identify ways of eliminating unsatisfactory performance.] 3.3 QUALITY CONTROL QUALITY CONTROL IS DEFINED AS THE MONITORING AND CONTROLLING ACTIONS REQUIRED DURING A PROJECT. CURRENTLY, THE PROJECT TEAM HAS PLANNED AND ACCOUNTED FOR THE DOCUMENTATION OF QUALITY ISSUES WITHIN THE ISSUE LOG (WBS 7.1.1). ONCE THE DEPLOYMENT TEST BEGINS IN DECEMBER 2009, THIS LOG WILL BEGIN TO BE POPULATED; ANLAYSIS CAN BEGIN SOME PERIOD AFTER THAT. THE ANALYSIS WILL INCLUDE IDENTIFYING SPECIFIC ISSUE CATEGORIES. THIS WILL FACILITATE THE USE OF PARETO ANALYSIS TO DOCUMENT THE FREQUENCY OF OCCURRENCE OF EACH ERROR/ISSUE TYPE. Page 3 of 6

4 Appendix A: Project Quality Management Plan Approval The undersigned acknowledge they have reviewed the Developing a Freight Congestion Mitigation Program Design & Technical Architecture Document Project Quality Management Plan and agree with the approach it presents. Changes to this Project Quality Management Plan will be coordinated with and approved by the undersigned or their designated representatives. Signature: Print Name: Title: Role: Date: Signature: Print Name: Title: Role: Date: Signature: Print Name: Title: Role: Date: Page 4 of 6

5 Appendix B: References The following table summarizes the documents referenced in this document. Document Name and Version Description Location Page 5 of 6

6 Appendix C: Key Terms [Insert terms and definitions used in this document. Add rows to the table as necessary. Follow the link below to for definitions of project management terms and acronyms used in this and other documents. The following table provides definitions for terms relevant to this document. Term Definition <term> <definition> <term> <definition> <term> <definition> Page 6 of 6