The course is part of this learning path
The course focuses on the components of the method and how they help to structure project delivery. Delegates should note that evening work will be assigned which is not expected to exceed two hours per night.
Specific course content will include:
- The structure of the method and the guide will be introduced before we discuss the context within which a PRINCE2 project operates.
- The seven PRINCE2 principles provide the framework for managing the project and are built on good practice developed from successful and failed projects.
- Themes and Processes
The seven PRINCE2 themes are aspects of the project that must be continually addressed and integrated as the project journeys through its life cycle.
- Business Case
The seven PRINCE2 processes encompass the chronological activities that are required to direct, manage and deliver the project successfully. The activities include pre-project, initiation and delivery, and end with project closure.
- Starting up a Project
- Directing a Project
- Initiating a Project
- Controlling a Stage
- Managing Product Delivery
- Managing a Stage Boundary
- Closing a Project
PRINCE2® is a [registered] trade mark of AXELOS Limited, used under permission of AXELOS Limited. All rights reserved.
The Swirl logo™ is a trade mark of AXELOS Limited, used under permission of AXELOS Limited. All rights reserved
- Welcome to Module eight part three where we finish off the quality theme. And here we're going to be looking at the different roles and responsibilities and the names for those roles. There are three product quality responsibilities that they need to know about. First of all, who is the producer? So the producer might well be the team manager but it might be a named team member who is responsible for producing the specialist product. Secondly, who's going to check that this product is fit for purpose, we call them a reviewer and then effectively they're carrying out quality control for us. And then finally, who is the approver? So the producer makes the product. The reviewer tests the product but the approver will check that the test was carried out properly and that all the documentation is there, and that the product is therefore fit for purpose. So we have these three different roles for each of our products or specialist products that it will be clear who is responsible for what to say who's producing, who's reviewing, who's approving. This would be recorded in the product description for each product and also in the quality register so that everybody understands what their responsibilities are at a particular given moment for a particular given test for a particular given product. There are a few other roles names that might pop up and particularly if you are looking at quality testing, written documents, you might well come across the quality review technique. Now this isn't explicitly mentioned in the practitioner exam sympus. However, being aware of all the processes and procedures is. So I think that this might be quiet a good idea if you just do run through this with me and you'll find some guidance on this in section 8.4 So this is a recommended technique by Prince2. And the quality review technique is a really good technique. If you have got documents or designs or products, generally that need a discussion in order to decide whether or not they are fit for purpose. And when you carry out the quality review technique, there are three parts to it. Firstly, we prepare for the review meeting. Then we have the review meeting and then there are usually some followup activities that we then have to carry out. So I'm just gonna go through these, you can read more in the chapter if you want to find out more, but this is really with a view to introduce some of the different responsibilities involved. If you're carrying out the review technique, you will have to have a chair. A chair will ultimately control the proceedings. They will be listed in the quality register and in the project product description having this responsibility. They will initially though check that the product is ready to review and they might get in contact with the presenter who will be presenting at the review meeting. The presenter then distributes copies of the product to everyone involved. So our reviewers and the chair and our administrator, which we're going to talk about later and also they'll include not just the product, but the product description for it. So we can see what the product looks like. And also what's supposed to be in it in the product description. The reviewers then will take a look at the products. They review it. If they've got any questions, they'll add them to a question list. They may even annotate the product itself, particularly if it's a document and they've spotted a typing mistake or a spelling error. The chair brings together all those questions into one question list and sends that to the presenter and the presenter therefore has an opportunity to prepare for the review meeting, with answers ready for those questions. And then the day of the review arrives and the presenter presents the product and the chair controls the proceedings, inviting discussion regarding the questions from the reviewers. The administrator is there, they're recording, any actions any responsibilities that have been allocated to those actions. And then from those discussions, the chair decides the results. The chair then will inform everyone involved as to the results of the review meeting. And there will probably be a number of followup actions. particularly if there are a number of flows of the product, it might be that we have to completely book a whole new quality review meeting. But if there's just a few things to follow up, the presenter will coordinate those actions. The reviewers will then sign off those actions that they've been allocated to sign off. The chair will sign off the whole product when all of those actions have been completed. And the administrator then is doing the important job of communicating that around the project and storing any quality records. Meanwhile the presenter formally requests approval for the product. So there's quite a few different roles there. So we did have our producer, reviewer and approver, but now we have a chair, presenter, reviewers and the administrator. So there are a couple of other roles here, that have been now it talks about in this quality review technique and if you probably do something like this. If you have ever been asked to read over documents, you have been a reviewer. Whether there was a formal review meeting or not. So most of the people involved in projects these days are having some kind of formal review for their written documents. But whether or not you call it the quality review technique, who knows that will be tailoring folks. you've just tailored Prince2 and you got a slightly different method in there. but that's it for now that completes our quality thing.
A hard working, self-motivated and dedicated IT Consultant with extensive experience and a proven track record in the areas of Management, Networking, Communications and Security. A capable organiser, quick to grasp and make good use of new ideas and concepts. Reliable and conscientious in all work aspects. Possesses exceptional interpersonal skills and utilises communicative abilities to build, develop and maintain effective relationships. A motivational and inspirational manager, who enjoys being part of a successful and productive team, and thrives in highly pressurised and challenging working environments.