From 1st July 2014, AXELOS, the joint venture company that has taken over responsibility for the PRINCE2 credential, will recognise the PMP and CAPM qualifications as acceptable alternatives to the PRINCE2 Foundation qualification.
Previously, passing the PRINCE2 Foundation qualification was a mandatory requirement for sitting the Practitioner level exam (although most people did both exams on the same day). From July AXELOS will recognise qualifications awarded to Practitioner candidates by the Project Management Institute (PMI) and the International Project Management Association (IPMA).
The Foundation qualification is a relatively straightforward 75 question multi-choice exam with a 50% pass mark so whilst welcome, this concession by AXELOS does not in any way suggest equivalence between the qualifications.
For more on the various project management certifications available see: http://www.mosaicprojects.com.au/PDF_Papers/P138_PM_Credentials_Aus.pdf
The complete refresh of the PRINCE2® project methodology and credentials is over and the 2009 version has been released.
PRINCE2 is a project management framework which has wide acceptance in many government areas. The intellectual property of PRINCE2 belongs to the British Crown which has placed the methodology is in the public domain.
Projects in Controlled Environments explains the name and the operative word is ‘controlled’. The business remains in control of its projects and everything in the method can trace back to this fundamental principle. This means the methodology works well in environments where the same organisations is the client and the primary ‘performing organisation’ for the delivery of the project.
The 2009 refresh has:
- Added 7 principles that were previously implied.
- Changed 8 Components into 7 Themes (Configuration Management has become part of the Change Theme).
- Reduced 8 Processes to 7. The former Planning process is dealt with as part of the Plans Theme.
- Added a new chapter on tailoring PRINCE2 to the environment in an attempt to reduce criticisms of the amount of bureaucracy involved in the methodology.
- A Benefits Review Plan is now created as part of Initiating a Project and updated at end of each stage. Benefits Reviews may occur at the end of stages as well as after closure and the concept of dis-benefits has been introduced. Interestingly, the Senior User is held to account for the realisation of benefits (ie, the customer).
- The Risk Management chapter has been rewritten to align with other OGC Standards. Response types cover opportunities as well as threats and a Risk Management Strategy introduced.
- A smaller book focused on the needs of project sponsors ‘Directing Successful Projects with PRINCE2’ has been released.
The structure of PRINCE2:
The 7 principles which are considered universal and self-validating must exist in every project run according to PRINCE2. They are:
- Continued business justification
- Learn from Experience
- Defined Roles and Responsibilities
- Manage by Stages
- Management by Exception
- Focus on products
- Tailor to suit the project environment.
The 7 processes are outlined in the diagram above. Underlying these processes are the themes presented in the methodology and these amount to best practice in a project environment. They answer questions about what, why, who, when, how, how much and provide clarity. The Themes are:
- Business Case
PRINCE2 -v- PMBOK
The primary difference between PRINCE2 and the PMI/ PMBOK® Guide view of projects is the boundaries. PMI (and most likely the new ISO21500) see a project starting when it is initiated by the client and completing once the outputs defined in the project charter are delivered. This is quite likely correct from a project practitioner’s perspective.
PRINCE2 sees the project starting much earlier and continuing through to the realisation of value by the organisation. This is quite likely correct from the perspective of an organisation initiating and managing internal projects.
There is very little difference in terms of the processes used to run a project between PRINCE2 and the PMBOK. What is different is PRINCE2 is totally focused on managing internal projects with organisational managers having a direct say in the management of the overall process and it provides an effective methodology for this circumstance. The PMBOK® Guide is a pure PM standard and has a more generic set of processes that can be adapted to a much wider range of circumstances and used in any situation (eg, a traditional project where the client contracts the project delivery organisation).
Which is best? What do you think??
We will continue to focus on the PMI range of credentials with our training mainly because of their wider application. PRINCE2 works well in the right circumstances. Whereas, the PMI range of standards seem to apply to most circumstances. But I suppose that is the key difference between a methodology and a generic standard.
Earlier this week, I was reviewing proposed abstracts for the PMOZ project management conference in Australia. One paper proposed comparing the PRINCE2 Methodology with the PMBOK Methodology.
The paper did not get accepted because its basic premise is completely wrong! The PMBOK® Guide is not and never has been a methodology.
Methodologies define the processes, responsibilities and workflows needed to achieve an objective. PRINCE2 is a good project methodology for managing projects with a large internal component. Agile and Waterfall are two different software development methodologies that incorporate elements of project management.
The PMBOK® Guide is an international standard. To give it its full name, it is A Guide to the Project Management Body of Knowledge. The processes described in the PMBOK® Guide are generally accepted good practice that apply to most project most of the time. This is the foundation for a good project management methodology but the PMBOK® Guide is not, and cannot ever be a methodology without adaptation.
The step between the PMBOK® Guide and a methodology is determining what, who and how:
- What of the processes should be applied in you organisation, to what extent and with how much rigour?
- Who is responsible for the implementation of the processes, including; generic roles and responsibilities, project org. structures and governance committees
- How the processes will be applied, templates, guidelines and workflows.
These are critically important issues.
- If a PMO sets out to ‘implement the PMBOK’ you are heading for disaster.
- If the same PMO sets out to develop a tailored methodology based on the good practices described in the PMBOK you are potentially on the right road.
Certainly in my business, if someone does not know the difference between a standard and a methodology, I tend to start asking a lot more questions about their competence. Having been involved in the last two upgrades of the PMBOK® Guide I consider it to be a very valuable resource to underpin the development of any project management methodology but you still need to do the hard work of determining the what, who, how and ‘how much’ for yourself to build the methodology and optimise the outcomes for your organisation.