<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1907245749562386&amp;ev=PageView&amp;noscript=1">

The Leonardo Blog

All Posts

Selecting a Project Management Model (PMM): Prince2 vs PMBOK


Business Improvement projects can be, by their very nature, interesting projects to run as they do not always seem to follow a traditional Project Management Models (PMM). Currently there are a number  of different Project Management Models available and widely used to manage projects. With a bit of knowledge about how the PMM works, the advantages and disadvantages of the different models, you can use them to provide the structure and governance required to execute a successful Business Improvement project.

The two most common Project Management Models (PMM’s) are PRINCE2 (Projects IN Controlled Environments) and PMBOK (Project Management Body Of Knowledge). There are also a number of in- house models that have been developed to address specific requirements within that organisation. Often, regardless of which model is used there are numerous benefits of adopting a companywide Project Management Model and using this model to execute your Business Improvement projects.

Advantages of the adoption of the regulated Project Management Models are:

  • If a company does not have an established PMM, the adoption and implementation of a regulated model enables them to very quickly build up a level of operational best practice due to the information and combined experience within PMBOK and PRINCE2
  • It creates an understanding within an organization of what is expected of a project team; It can give a company a competitive advantage;
  • Users can gain recognized ‘qualifications’ in the model; Training is easily managed;
  • It creates a community which in turn gives employees opportunity to share best practice.

Below we outline some of the advantages and disadvantages of the two big PMM’s and the establishment of an in-house model that was undertaken by a large Australian organization.


PMBOK and PRINCE2 are two different approaches to Project Management that are widely used. Both of these PMM’s very definitely complement each other. Both approaches have advantages and disadvantages but the identification of the advantages and disadvantages of each approach is dependent on the environmental context being used to compare the two.

What is PMBOK?

PMBOKPMBOK is a collection of best practice principles that incorporates the different knowledge areas and process groups within a project. The PMBOK describes what a Project Manager should know to successfully execute a project.

PMBOK has 39 processes grouped in 9 knowledge areas or 5 process groups.



  • Comprehensive approach;
  • Well suited to an iterative development environment; Includes Project Procurement Management; Customer Requirements driven;


  • Project Governance is around the use of a Project Sponsor and stakeholders; Descriptive approach;
  • Looks at a project as a single entity;

What is PRINCE2 ?

PRINCE2 is a structured, process based on a series of components and techniques. PRINCE2 describes what a project manager should do to successfully execute a project by supplying a road map that advises how a Project Manager should organise, manage and control their projects. The primary focus of PRINCE2 is the Business Case.

PRINCE 2 has 44 processes in the eight process groups and the interactions between the process groups are shown below.



  • Business case driven; Process based methodology;
  • Clear quality management points within the process; Change control process;
  • Project governance is around the appointment of Project Board (PB). This has its own set of advantages:
    • Increases the Business buy in as they are consulted via the PB throughout the lifecycle of the project;
    • The PB has members that have the ability to assure resources;
    • Decisions are made by the Business that effect the business;
  • Focuses on key risk areas within a project environment;
  • PRINCE2 can be integrated with a number of other models:
    • OGC Gateway Process
    • Managing Successful Programs (MSP)
    • CMMI
    • ITIL


  •   There is a requirement to produce numerous products (documents) throughout the project lifecycle;
  • Decisions are made by the PM. This can lead to ‘paralysis by analysis’;
  • Does not include all of the knowledge areas and detail found in the PMBOK (Procurement and HR);
  •   Not as suitable to an iterative development approach;


PRINCE2 vs PMBOK - retaining the benefits of each and correcting for the deficiencies

Both approaches are global and have hundreds of thousands of certified members. It is generally accepted by most Project Management Professionals that PRINCE2 and PMBOK are complementary and that a competent Project Manager should have knowledge of both.

The approach that is being adopted by many Australian businesses is to establish an internal model that is principally based on one PMM with some additional process that incorporates the aspects of the  other PMM’s available.

A large Australian organization was presented with the challenge of modelling a best fit Project Management approach to deal with the large variety of projects undertaken within the organization. The type of projects undertaken by this organization include anything from Process Improvement to IT system upgrades to major infrastructure projects. Described below is the analysis that went behind the design of the internal project management model.

The directive was that the organization required a comprehensive Project Management model to:   

  • Address the needs of the project, and also the organization;
  • Ensure that the risk of failure is managed, the method must provide the correct level of control and reporting;
  • Provide the correct level of management information so that the appropriate decisions can be made;

A bespoke project approach was designed after a survey of the business was conducted. Through the receipt of the surveys the team identified a number of both positive and negative project management characteristics visible at that time throughout the organization.

With the design of the new methodology the team analyzed both PRINCE2 and PMBOK for the strengths of each approach. They mapped the strengths of the different models to the issues identified by the business. They then incorporated all of these different strengths to a methodology that was designed to:

  • Reduce the risk of project failure; Focus on the needs of the business;
  • Ensure the correct involvement of the correct teams at the right time; Provide a consistent way to plan and manage projects;
  • Provide reporting visibility via effective controls;
  • Ensure appropriate accountability and authority over projects;

The result of this exercise was a series of project based activities that were tailored specifically to meet the needs and environment of this particular organization.

Based on the experience of the team and the following analysis, the initial decision was made to customize the PRINCE2 method of Project Management. As both the PMO and the organization have matured, the method has been further customized to incorporate elements of PMBOK in order to utilize the advantages provided by both models.

The in-house model identified that:

  • Even for a small project, no steps should be skipped; however the formality with which they are performed may vary greatly from small, medium and large projects.
  •  The same applies to the manner in which Project Management products are documented a single page may be sufficient for a certain document in small projects, but larger projects would likely require more detail.
  •  The method itself also has to encourage feedback and continuous improvement.

In addition to this the organization has also incorporated the OGC Gateway model into their in-house model. The main driver for this inclusion was in order to further impress the requirements for good process governance and control and to provide on-going feedback to sponsors and stakeholders on project ‘health’.


Ultimately it doesn’t matter what Project Management Model you use, just as long as you use one. There a numerous advantages and disadvantages of the two principal PMM’s, but with a firm understanding of what your organization requires from a PMM you can either, adopt and implement a regulated Project Management Model or if you have some time you can successfully cherry pick from both PRINCE2 and PMBOK to create a in-house model that works for your organization.


Watch 7 Enablers of BPM Video

Related Posts

Leonardo wins 2020 Red Hat ANZ Professional Services Partner of the Year

Red Hat announced Leonardo as their 'ANZ Professional Services Partner of the Year'. This is the third year in a row Leonardo has been recognised at these regional awards, and we're extremely honoured again for this acknowledgement. Well done to Team Leonardo for your superb work delivering great outcomes for clients - and to Red Hat Asia Pacific for their amazing partner growth and results over the past year.

Leonardo Invests in Apromore to advance AI-Driven, Open-Source Process Mining Technology

MELBOURNE, AUSTRALIA – 7 July 2020 – Leonardo today announced its investment in Apromore - a leading developer of open-source, AI-driven process mining technology. The investment forms part of a Series A round of funding totalling $A6.8 million, led by German business process management specialist GBTEC, and also included The University of Melbourne, which helped to incubate Apromore prior to spin off.

Leonardo wins 2019 Red Hat Hackathon - Customer Experience with OpenSource

      We're thrilled to share with you that Leonardo has won 2019 Red Hat Hackathon 'ReBoot Customer Experience with Open Source'. Early on Friday morning ( 5am AEDT 13th December 2019),  Leonardo awarded first place from a field that included 320 participants from across the globe.  The Hackathon's brief was to reinvent customer experience using Open Source. Providing an outstanding customer experience that customers actually love is especially challenging in more traditional industries like banking, insurance, telecommunication, public sector/government, healthcare, manufacturing, or transportation. These markets offer great opportunities for change and disruption as has been shown by many examples such as Uber disrupting transportation, Twilio disrupting telcos and Stripe or Transferwise disrupting banking.  We want you to be the next disrupter who creates a customer experience that users actually love.  An Open Source solution - ACE  Airline Customer Experience Our project is an application using a Red Hat Process Automation Manager process-as-microservice developed for "ACE Airlines", our fictional client (see video above for the demo). It communicates personalised, event-driven (gate change, delay, etc.) messages to passengers in the language of their choice, using their preferred communications type (SMS, push notification, email).