QUALITY MANAGEMENT PROCEDURE I NFORMATION T ECHNOLOGY S ERVICES Version: Doc Security: Author: Date: 0.1 Public Peter Woolley 10/07/2013 Quality Management Procedure C ONTENTS Purpose..................................................................................................................... 3 Related Documents .................................................... Error! Bookmark not defined. Quality Requirements ................................................................................................ 3 Quality Objectives .................................................................................................. 3 Procedure Requirements ....................................................................................... 3 Quality Management Strategy ................................................................................... 5 Approach ............................................................................................................... 5 Responsibilities ...................................................................................................... 6 Quality Metrics .......................................................................................................... 7 Approval Cycle .......................................................................................................... 7 Change History ......................................................................................................... 7 Page 2 of 7 Quality Management Procedure P URPOSE The purpose of the Quality Management Procedure is to: To define the project’s quality requirements and responsibilities. To describe how the quality of the project will be managed and what is required to achieve this. Q UALITY R EQUIREMENTS Q UALITY O BJECTIVES The following quality objectives will have to be fulfilled by the project. Project related quality objectives: The project will be completed according to the approved schedule as defined within the PMP and any approved Change Requests. The project will be conducted according to any and all associated contracts between Flinders University and third party suppliers. All project deliverables, including documents, code, test results, implemented systems and hardware will be presented to the relevant project stakeholders for review and approval according to approved delivery schedule. The relevant project stakeholders will review deliverables in a timely manner allowing updates and final approval within the approved delivery schedule. Product related quality objectives: The project stakeholder review is intended to ensure that the project deliverables meet all approved specifications. P ROCEDURE R EQUIREMENTS The following table defines the Project Management procedures and deliverables that will be used in the running of the project. Collectively these processes and procedures form the basis of the quality plan that will be used on the project. The Project Manager is responsible for ensuring that all relevant the project management deliverables listed in the table below are created and applied for the project. Page 3 of 7 Quality Management Procedure Procedure / Deliverable Name Project Management Plan Procedure Description To capture the essence of the project in terms of project profile, conditions, and planning and success criteria of the project. To clearly state the project scope boundaries for the solution to be delivered (what is included, what is excluded), and the related responsibilities. Also includes: Business Case Identification of Stakeholders Communication Plan Deliverable Review and Acceptance Procedure Work Break Down Structure Project Organisation Structure and definition of Roles and Responsibilities Release Plan Scope Management Plan Deliverable Review and Approval Process To manage the scope of the project throughout its lifecycle Communication Management Procedure To define the communication activities, roles and responsibilities, frequency etc that are to occur throughout the project. Procurement Management Procedure To define the process in which procurement is undertaken for the project. The procurement plan is contained within the PMP. Assignment Descriptions To define the assignment for each individual on the project Team. To evaluate the success of a resource's assignment. To serve as a reference for individual performance assessment Task Effort Tracking To serve as a mechanism to record actual effort spent on project tasks and for estimating effort remaining to complete tasks. To support project tracking of delivery schedule and cost To specify who will be responsible for managing the project's risks and issues. To specify the project's risk and issue management process. To specify the parameters to be used when evaluating and classifying the project's risks and issues Risk and Issue Management Procedure Project Risk Assessment To rate the project in terms of pre-defined categories. Project Financial Report To record and track the financial performance of the project. Work Break Down Structure Refer PMP Key Decision Log To record and centralise key decisions Change Requests To formally document changes the project. To provide information to facilitate stakeholders making a decision regarding a change request Change Request Register To formally document and keep track of a requested change to the project. Risks and Issues To describe project risks, and document the analysis and decisions taken on them. To describe project issues, and what was done, is being done, and will be done about to resolve them. Risk and Issue Register To track the project risks and issues. Defect Management To record, assign severity, assess and analyse, assign to resources, record resolution and track defects found throughout the testing process of a project. Defect Register To formally document and keep track of defects raised throughout a project. Status Report To provide an overall status on project performance based on preestablished performance indicators, at a pre-established frequency. To facilitate the project control and decision-making processes Page 4 of 7 Quality Management Procedure Procedure / Deliverable Name Procedure Description Work Schedule To organize and assign work items in accordance with the selected release strategy identified in the Master Plan To establish the project schedule baseline and progress tracking items To communicate responsibilities for identified deliverables Project Completion Report To evaluate the project with regard to its initial success parameters. To provide feedback to the client, stakeholders, and members of the project team Human Resource Plan To list the responsibilities of each resource within the project team. To describe when and how human resources will be brought on and taken off the project team. To identify the competency required for each identified role. To establish and communicate the activities that will take place to develop the expected competence from team members Development Process To define the process to be followed to produce the project deliverables. This process identified the quality reviews actions that are to be undertaken and who undertakes these reviews. This process is defined within the PMP. Implementation Plan To plan production implementation and post-implementation activities. To describe and quantify resources required to implement the system. To describe and quantify resources and that will use, operate, support, and maintain the system once implemented This process is defined within the PMP. Q UALITY M ANAGEMENT S TRATEGY A PPROACH The overall quality management strategy to be used on the project can be summarised by the following steps: Create – a deliverable Review – the deliverable goes through a review process which will vary depending on the type of deliverable Correct – the deliverable is updated with review feedback Approve – the deliverable is approved by the relevant party The reviews are the foundation of the quality plan for the project and product. The reviews are classified into the following three categories: process, project, deliverable. Process Review Compliance with Quality Plan At times Flinders University ITS will audit the delivery processes of the project to ensure that it is complying with the requirements of this Quality Plan. The Project Manager will make all project files and other relevant documentation available to the auditors. The first of these audits will be a project start-up review conducted in the first week of the project. Page 5 of 7 Quality Management Procedure Project Review Project Status The Communication Plan defined in the PMP describes the project status reporting in terms of frequency of formal status reporting attendees to the review the distribution list for the status report The status report is produced to provide the following information: project progress; status of resolution of risks and issues; status of change requests; and financial status. Monthly Project Review Each month Project Services management will review the project. The objective is to ensure that the project is being executed according to schedule, budget and quality criteria. Risk and Issue resolution actions are also reviewed. Any appropriate corrective actions will be assigned to appropriate resources. Actions are recorded and distributed. Deliverable Review The process to accept the deliverables is as defined in the Deliverable Review and Acceptance process, in the PMP. R ESPONSIBILITIES Responsibilities Who Define, implement, and control the quality program for the project Project Manager Ensure that the project (processes and products) satisfies the requirements of this Quality Plan Examine and escalate, as required, any reported deficiency Ensure timeliness of each required user intervention (as scheduled) Project Manager Ensure the quality of the products and deliverables Delivery Team Make critical decisions regarding the project and its product Business System Owner Ensure compliance with the Configuration Management procedure Project Manager Page 6 of 7 Quality Management Procedure Q UALITY M ETRICS The quality metrics to be applied to the project are defined within the PMP Deliverable Acceptance Criteria. A PPROVAL C YCLE Role Name Signature Date Reviewer(s): Approver(s): C HANGE H ISTORY Version (State) Author Change Description Date 0.1 Peter Woolley Original draft 21/61/2013 Page 7 of 7