The PRINCE2 Guide
Accessibility

Background
Twitter: @RuleWorks The PRINCE2 Guide RSS Feed


PRINCE2 Update - 2009 Edition

The PRINCE2 Manual has been updated in June 2009. There are no major differences between the 2005 and 2009 versions of PRINCE2 methodology. The PRINCE2 methodology has been refreshed and not re-written.

PRINCE2 keeps its core value of being a universal method that can be applied to any project regardless of type, scale, culture or geography. The improvements are based on user feedback on what was liked/disliked about PRINCE2 and on the different challenges that face today’s projects. The key improvements to PRINCE2 2009 are:

  • PRINCE2 is less prescriptive and more flexible
  • PRINCE2 is less theoretical and more practical
  • PRINCE2 now has a set of clearly defined principles. These principles can be used as a check that PRINCE2 is being applied in the spirit in which the method has been designed – not too rigidly nor superficially
  • The need to tailor the method is explicitly stated and guidance on how to tailor is provided
  • The linkage with other standards and bodies of knowledge is clearly shown
  • The importance of the soft aspects of project management are emphasised
  • PRINCE2 is not bureaucratic – the method requires information and decisions, not documents and meetings.
PRINCE2 2009 and 2005 Comparison
Area PRINCE2 2009 Edition PRINCE2 2005 Edition
Principles 7 principles None
Themes / Components

7 themes:

8 components:

  • Business case
  • Organization
  • Plans
  • Controls
  • Management of Risk
  • Quality in a Project Environment
  • Configuration Management
  • Change Control.
Sub-processes 40 activities comprising recommended actions. No codes. 45 codified sub-processes comprising prescriptive actions.
Techniques

2 techniques explained

  1. Product Based Planning
  2. Quality Review

Numerous cross-references to techniques from other bodies of knowledge, including ‘soft’ aspects.

3 techniques explained

  1. Product Based Planning,
  2. Change Control,
  3. Quality Review.
Project Environment

Context rich guidance on tailoring the method according to the project’s environment, including:

  • Projects in a programme
  • Commercial customer/supplier relationships
  • Multi-owned projects
  • Alignment with other lifecycle models and bodies of knowledge
  • Project scale.
Not covered.
Management Products 26 management products with explicit guidance on their evolution and which ones can be combined. 36 management products.
Roles

8 roles

  1. Project Board,
  2. Senior User,
  3. Executive,
  4. Senior Supplier,
  5. Project Manager,
  6. Team Manager,
  7. Project Assurance,
  8. Project Support.

Suggested competences for each role. Project Board roles now include “duties and behaviours”.

10 roles

  1. Project Board,
  2. Senior User,
  3. Executive,
  4. Senior Supplier,
  5. Project Manager,
  6. Team Manager,
  7. Project Assurance,
  8. Project Support,
  9. Configuration Librarian,
  10. Project Support Office.
Checklists Process based checklists. Governance checklist aligned to APM’s governance principles. Component based checklists.
Project Board guidance

Role specific guidance for senior managers who sponsor or direct projects, including:

  • What makes a good Project Board
  • Suggested agendas for Project Board reviews
  • Checklist of key decisions for each Project Board review
  • Pre- and post-project responsibilities.
Embedded within the main guide and aimed at Project Managers rather than Project Board members.
© 2010 RuleWorks - All Rights Reserved - Policy - - Sitemap