Relationship between the Project Management Body of Knowledge (PMBOK) and PRINCE2™

http://www.ppi-int.com/prince2/prince2-pmbok-relationship.php

As noted in the Introduction to the PMBOK Guide (Project Management Institute 1996) the term PMBOK is an inclusive term that describes the sum of knowledge within the profession of project management.

It is therefore a knowledge-based approach that covers the entire vast subject of project management. The PMI Guide to the PMBOK identifies and describes that subset of the entire PMBOK which is generally accepted as applicable to most projects most of the time.

The PMI Guide to the PMBOK is therefore an extremely useful reference document and is often the basis of generic project management training.

PRINCE 2 is a process-based approach to project management. It provides a process model (of eight processes) that is intended to be applied as a set of steps in a logical sequence by a project manager in planning and managing a project.

The application of the process model is adaptable to most types of projects and a wide range of complexity. In addition the PRINCE2TM manual (Managing Successful Projects with PRINCE2TM) includes a number of 'Components' that are guidance for a project manager in applying the process model. These Components have similarity to the PMBOK Knowledge Areas.

The PMBOK details a set of processes that fall under nine Knowledge Areas and can be linked in five groups if the project manager chooses.

The underlying difference between the PMBOK and PRINCE 2 is that the PMBOK offers the project manager a considerable array of information about proven practises in this field and invites the project manager to apply these where they deem appropriate whereas PRINCE2TM provides a more prescriptive (although flexible) set of steps for the project manager and teams to follow.

As one might expect, it is apparent that the knowledge areas of the PMBOK and the processes and components of PRINCE2TM cover many common topics. Apart from a number of terminology differences it is clear that both represent 'best practice' with their variance being in the implementation as a methodology.

The PRINCE 2 approach has the advantage that (because it is somewhat prescriptive) it causes a degree of standardisation in an organisation. Whilst allowing for tailoring to a range of projects it generally requires all projects to undertake the same steps (processes) and use the same terminology. This has obvious benefits in corporate programme management, project staff training programs, and project performance and tracking systems. The disadvantage may be that it potentially constrains creativity in the variety of methods applied to managing a project.

Several organisations have recognised that there are benefits in allowing both PMBOK and PRINCE2TM to co-exist. PMBOK provides the academic knowledge resource that is useful in enhancing the profession of project management. PRINCE2TM provides a useable process model that can be applied directly by project managers and teams from a diverse range of backgrounds to produce consistent project management and project outcomes.

PRINCE2TM PROCESSES

 

STARTING UP A PROJECT

SU1

Appointing a PB Executive and a PM

SU2

Designing a PM Team

SU3

Appointing a PM Team

SU4

Preparing a Project Brief

SU5

Defining Project Approach

SU6

Planning an Initiation Stage

   
 

INITIATING A PROJECT

IP1

Planning Quality

IP2

Planning a Project

IP3

Refining the Business Case and Risks

IP4

Setting up Project Controls

IP5

Setting up Project Files

IP6

Assembling a PID

   
 

PLANNING

PL1

Designing a Plan

PL2

Defining and Analysing Products

PL3

Identifying Activities and Dependencies

PL4

Estimating

PL5

Scheduling

PL6

Analysing Risks

PL7

Completing a Plan

   
 

DIRECTING A PROJECT

DP1

Authorising Initiation

DP2

Authorising a Project

DP3

Authorising a Stage or Exception Plan

DP4

Giving Ad hoc Direction

DP5

Confirming Project Closure

   
 

CONTROLLING A STAGE

CS1

Authorising a Work Package

CS2

Assessing Progress

CS3

Capturing Project Issues

CS4

Examining Project Issues

CS5

Reviewing Stage Status

CS6

Reporting Highlights

CS7

Taking Corrective Action

CS8

Escalating Project Issues

CS9

Receiving Completed Work Package

   
 

MANAGING PRODUCT DELIVERY

MP1

Accepting a Work Package

MP2

Executing a Work Package

MP3

Delivering a Work Package

   
 

MANAGING STAGE BOUNDARIES

SB1

Planning a Stage

SB2

Updating a Project Plan

SB3

Updating a Project Business Case

SB4

Updating the Risk Log

SB5

Reporting Stage End

SB6

Producing an Exception Plan

   
 

CLOSING A PROJECT

CP1

De-commissioning a Project

CP2

Identifying Follow-on Actions

CP3

Project Evaluation Review

 

PMBOK PROCESSES

 

INITIATING

5.1

Initiation

   
 

PLANNING

 

Core Processes

5.2

Scope Planning

5.3

Scope Definition

6.1

Activity Definition

6.2

Activity Sequencing

6.3

Activity Duration Estimating

6.4

Schedule Development

7.1

Resource Planning

7.2

Cost Estimating

7.3

Cost Budgeting

4.1

Project Plan Development

   
 

Facilitating Processes

8.1

Quality Planning

9.1

Organisational Planning

9.2

Staff Acquisition

10.1

Communications Planning

11.1

Risk Identification

11.2

Risk Quantification

11.3

Risk Response Development

12.1

Procurement Planning

12.2

Solicitation Planning

   
 

EXECUTION

4.2

Project Plan Execution

   
 

Facilitating Processes

10.2

Information Distribution

9.3

Team Development

8.2

Quality Assurance

5.4

Scope Verification

12.3

Solicitation

12.4

Source Selection

12.5

Contract Administration

   
 

CONTROLLING

10.3

Performance Reporting

4.3

Overall Change Control

   
 

Facilitating Processes

5.5

Scope Change Control

6.5

Schedule Control

7.4

Cost Control

8.3

Quality Control

11.4

Risk Response Control

   
 

CLOSING

12.6

Contract Close-out

10.4

Administrative Closure

 

PRINCE2 Exam - Sydney, Melbourne, Brisbane

Testimonial

"Arrived with no experience and leave with what I feel is a sound understanding"

Systems Engineering Course
delegate, Australia

We deliver over six-continents

Map

Have a question about our courses?

View our FAQ

Contact Us

Call us on:

Australia : +61 3 9876 7345
Brazil: +55 12 3212 2017
UK: +44 020 3286 1995
USA: +1 888 772 5174

View full contact details

Systems Engineering NEWSLETTER

SyEN makes informative reading for the project professional, containing scores of news and other items summarizing developments in the field of systems engineering and in directly related fields.