PRINCE2 Training: Background and Techniques

PRINCE2 is the acronym for ‘PRojects IN Controlled Environment’. This is a project management standard used extensively by the UK government. PRINCE2 training is based on structured methodology and is the registered mark of the ‘Office of Government Commerce’. PRINCE2 primarily focuses on when a project has to be delivered, what is to be delivered, why it is to be delivered and to whom. It puts emphasis on organized and controlled structured processes that recognize the responsibilities in a project. The project is divided into manageable and controllable stages that are keys to a product based planning approach.

A Brief History of PRINCE2 Training

In 1989, PRINCE became a standard for government projects, replacing PROMPTII. In October 1996, with some modifications it was re-launched as PRINCE2. A fundamental revision of the method was done in 2006 to make it simpler and adaptable to the changed business environment. PRINCE2 training was re-launched as ‘PRINCE2:2009 Refresh’. The name PRINCE2 was kept intact to show that the method is basically faithful to the principles of PRINCE2. Now, there are two manuals: ‘Directing Projects Using PRINCE2’ and ‘Managing Projects Using PRINCE2.’

Contemporary PRINCE2 Training Techniques

PRINCE2 is a standard methodology of project management that works in tune with the specialist techniques available and appropriate to the subject, sector and size of a project. Three contemporary PRINCE2 training techniques are:

Product Based Planning: This is the starting point for all planning activities and a requisite of PRINCE2 training technique. This is a process of identification for all products and deliverables of the project along with the allied work required to deliver them. The planning begins with the question; ‘what must be delivered’ rather than ‘what should be done’ and starts with the ultimate goal of the project, involving the customer from the very beginning.

Product Breakdown Structure (PBS): It is the hierarchical family tree of all the products and sub-products that ultimately compose the final product. Paper based products like approvals or quality checks of earlier products, test documentation; safety certification and so on may be included in the PBS.

Product Flow Diagram: Once the PBS is in place, a product flow diagram is prepared, identifying the order of precedence of products. There may be multiple and complex parallel paths and arrangements that lead to the development of a project.

Work Breakdown Structure: After the preparation of PFD, work can commence on defining the assignments required to produce them.

Change Control Technique: As many organizations have their own change control techniques, the approach of PRINCE2 training is an optional one. However, if adopted, the PRINCE2 change control technique provides simple and effective control of changes, concerns and issues that the project faces when it is on. The techniques primarily focus on minimal disruption of service, cost effective utilization of resources and reduction of back-out activities. A typical change control process involves:

Record: A formal request from the client for change is recorded and categorized by the change control team.

Assessment: The team of impact assessor determines the justification of change and sends it to the delivery team for planning.

Plan: The team assigned, plans the change in detail.

Test: The stakeholders agree with the plan and test it. An approval from the client and time is requested.

Implementation: With the consent of all stakeholders about the cost and time of implementation, the change is implemented and reviewed.

Close: When the client agrees with the change, it is closed.

Quality Review: In most cases, the end product of a project is documents. A structured and objective technique is offered by Quality Review to verify and check a draft document against an agreed standard or specification of that document. The producer, user and those assigned with quality assurance may all be involved in the process. The process primarily aims to identify any error in the product but does not provide any solution for it.

Also Read