prince 2

1303KM Project Management

PRINCE 2

2326IS - Supplementary Material

Learning Objectives

1. What is PRINCE

2. Project Organization

3. Project Planning

4. Project Control

5. Project Activities

6. Summary


1. What is PRINCE

• PRoject IN Control Environment• A standard in IT project management methodology

developed by the CCTA (Central Computer and Telecommunication Agency) of U.K. since 1970.

• Adapted by the ITSD of HK since early 1994.• Upgraded to PRINCE2 in 1998

• Items to be managed in a PRINCE project– Scope (function), Time, Cost, Quality, Risk


2. PROJECT ORGANIZATION


3. PROJECT PLANNING

• Planning– Product Based Planning: focus attention on goal

rather than on process

• Staging– breaking a project into stages enables more effective

management and control of project


3.1 Techniques for Product Based Planning

• Product Breakdown Structure (PBS)

• Product Flow Diagrams (PFD)

• Product Descriptions• Product Transformation ,


3.2 Benefit of Staging

• ESA provide discrete packages of work to be review by senior management and make objective assessments of the progress to date

• ESA facilitate control against project momentum to progress regardless of cost by reappraisal of business case

• More realistic estimation and monitoring before the commencement of next stage.

• Monitor of project is enabled within and at the end of each stage.


3.3 Staging Guidelines

• Each Stage should define:– Start & finish dates

– end-products to be produced

– resource needed to produce the end-product

• Stage setting should consider:– stage upon the completion of major end-product (not divide a

maj. end-product)

– stage at decision about the ongoing viability of project

– stage at critical points where visible tight control is necessary.


3.4 Plans for decision making and control

• Project level– Technical Plans– Resource Plans

• Stage level– Technical Plans– Resource Plans


4. Project Control

• Management by Exception

• Quality Control

• Control Meeting– Formal Assessment Meeting(PSC)– Checkpoint Meetings/Reviews(PM)

• Management of Risk

• Configuration Management


4.1 Management by Exception

• Time and Effort of PSC members are conserved and yet maintain the overall control of project by delegate the day-to-day project management responsibility to the PM and allocate a time & resource tolerance for running the project.

• amount of tolerance allocated on any one stage is assessed by the PSC in the light of the plans for the stage, the degree of risk associated with those plans, the criticality of that stage to the successful completion of the project, and the experience of the PM.


4.2 Quality Control

• Quality Plan included in the project Initiation Document for

outlining the overall Quality Expectation and Control of the

project at the outset

• Quality Criteria and Quality Checking Method(QCM) are

contained in the Product Description for quality standards and

quality control a detail level.

• Quality Review use QCM to apply to the product and Quality

Criteria will be the base for reference.


4.3 Control Meetings

• Formal assessment Meetings: Event driven meeting with necessary info. for decision making is circulated well in advance and Chairmen ensures the discussion is confined to real management issues.– Project Initiating Meeting– End-stage Assessment– Project Closure Meeting

• Checkpoint Meeting: regular time driven meeting held by PM


5. Project Activities

• Project Initiation– Project Initiation Meeting– Project Initiation Document (PID)

• Project Stages– Checkpoint Review – Highlight Reports (monthly) PM to PSC – End-Stage Assessments (ESA)

• Project Closure– Project Evaluation Report


6. Summary - Why PRINCE?

• Standard Project Management Method: staff move from one project to another can still aware of the roles, procedures, processes and reporting formats.

• Standard training materials, courses available, no need to redevelopment.

• Enable refinement over years of practice.


6. Summary - Why PRINCE ? (conti)

• It is a flexible method, suitable to many shape and size of project. Its particular strengths are:– Definition of the roles in a project

– involvement of user at all level in all aspects from beginning to end.

– insistence on establishing a business case before any major expenditure.


PRINCE Glossary

PSC Project Steering Committee

PM Project Manager

PAT Project Assurance Team

QCM Quality Checking Method

PBS Product Breakdown Structure

PFD Product Flow Diagram

PID Project Initiation Documents

ESA End Stage Assessment