Quality plan prince2 template

The benefits management approach is part of the PID and is prepared by the project manager. This process involves ensuring that a management stage remains within tolerance. It begins when a stage has been authorized to proceed by the project board, and the activities within it are mostly carried out by the project manager.

A work package is a task, or activity. Periodically throughout the work package, the project manager must monitor and control the work package to ensure it completes within tolerances. The issue register, risk register, and configuration item records are updated as required. The project manager must monitor and control the stage status to ensure that it completes within tolerance. The checkpoint reports provide crucial information.

If any issues arise, the issue register is updated and an Issue Report produced. Risks are periodically reviewed and re-analyzed to ensure their viability, resulting in an updated risk register. The stage plan is updated as necessary. Highlight reports are produced by the project manager and given to the project board. They update the project board at the interval agreed upon at the beginning of the project. Throughout the stage, issues will pop up. These issues are logged in the Issue Register.

Usually, an associated risk has occurred and the risk register requires updating as well. An Issue Report is created and reviewed by the project board, but this activity applies to issues that can be dealt with by the project manager without exceeding the stage tolerances.

If the issue cannot be dealt with without exceeding stage tolerances, an Issue Report is created and escalated to the project board for consideration of an exception. When an issue occurs, most often a new work package must be produced to implement corrective actions.

It is carried out primarily by the team manager, that is, the technical manager that carries out parts of the project, and reports to the project manager. Prior to beginning work on a work package, the team manager and project manager agree as to what is to be delivered.

The tolerances and quality levels are confirmed, and the requirements are well understood. The team manager creates a plan for the work package. This activity refers to the carrying out of the work by the project team, to produce the Specialist Products the products or services the project was created to produce.

At the conclusion of the work package, the Specialist Products are delivered and the work package is complete. The stage plan is updated. As the end of a management stage is approaching, this process kicks in. For example, the client may want a high-standard and low-energy apartment block.

This will require triple-glazed windows, thicker insulation and all fittings with a guarantee of 20 years. They must be listed in detail and with tolerance levels. They should be prioritized, starting with what the client finds most important. The Acceptance Criteria is a prioritized list of attributes that the Project Product should have when complete. This is first agreed between the Customer and Supplier in the very first process, the Starting Up a Project process. Think of a table in Excel or Word when you think about Acceptance Criteria.

The Project Product Description is written around the same time as the Acceptance Criteria and both can be updated during the Initiating a Project process. This Acceptance Criteria will be baselined with the rest of the Project Initiation Documentation and can only be changed with approval from the Project Board. Towards the end of the project, the customer will check that all the Acceptance Criteria have been met before the project can be closed. It is therefore a good idea to have agreed in advance on the acceptance methods that will be used.

The acceptance criteria should be agreed by the customer and supplier during starting up a project and documented in the project product description. The acceptance criteria will often need refinement during initiating a project, but once agreed will be under change control. Once again these things and not costing stand forever there may will be a reason to change acceptance criteria but once they have been agreed that under change controls are any changes need to go through a formal change control process.

The choice of acceptance methods is crucial as it is relied on to prove that project product is except. Premium Resources Training Courses. Quality Planning in PRINCE2 The purpose of quality planning It is to provide a secure basis for project board agreements on the overall quality expectations, products required together with their quality criteria, the means by which quality will be achieved and assessed and the associated acceptance criteria.

Measurements that can be used to assess Quality speed, size, noise, etc. Think of a Laptop PC description on a website just 2 or 3 pages. Create the Quality Management Approach document: This document defines the agreed strategy for Quality in this project or, in other words, the rules of engagement for Quality during the project.

Write Product Descriptions for each of the main products in the main product and include the Quality information, such as: This will be done for all the products that make up the main Project Product. Doors, walls, windows and fixtures. Quality criteria for each product and quality tolerances. Product-Based Planning which will be discussed later will provide a list of all products, and then you add the Quality information to each Product Description.

Quality method, i. Quality responsibilities for creating, quality checking and approving the product. Lastly, set up the Quality Register. At first, it will be empty. Some good questions to ask to get the customer focused on Quality: What percentage of features should work when product is launched, and what is the budget for critical issues e. Acceptance Method All Acceptance criteria have to be measured, inspected and approved, and this proof will have to be given for each Acceptance Criterion.

All documents will be made available to Product Development Manager, S. Jones during the project by the Project Manager. Acceptance Responsibilities Project Manager will collect all inspection, survey and other documents and hand them to the appropriate person s.

The Executive will confirm Project Costs and Manufacturing unit costs. Senior User will be responsible for all other Acceptance Criteria. The Quality Management Approach A Quality Management Approach is a document and a plan of action that defines the Quality requirements and the Quality Control method for all the products in the project. What standards will be used? What tools and techniques will be used?

How will Quality Assurance be carried out? What records will be required and where will they be stored? How will the timing of Quality activities be executed? Product Descriptions The Product Descriptions should be created for all the products as part of the planning activities and before the Project Plan can be completed. The contents are as follows again, notice how much Quality information : Identifier: Unique product name: e. Title: Name by which the product will be known: e.

Purpose State who needs the product, why they need it, and what it will do. Composition List the parts that the product will be made up of. Quality Criteria e. Color, noise, size, durability, lifetime. Quality Tolerance e. Quality Method e. Use machine to test color fading; use inspection. Quality Skills required e. What knowledge is required to be able to test. Quality Responsibilities e. Responsible for Producing, Reviewing and Approving. Quality Register The Quality Register The Quality Register is a diary of the Quality events that take place during the project, such as workshops, reviews, testing and acceptance.

Product ID: Just a product tracking number in the project ex: Quality Method: Describes how testing will be done. Producer: Who produces or installs the product, such as Otis an Elevator Co. Actual Review date: Actual date that Review happened. Result: This can be Pass or Fail. There are three parts to Quality Control, and I will explain each of them: Carrying out the Quality methods: e.