Tag Archives: PM2

EU Commission released new PM Methodology (PM2) guide

img_1959The guide was released by the centre of Excellence in Project Management Methodology (CoEPM2) of the European Commission.

The PM2 guide incorporates elements from globally accepted best practices, standards and methodologies.

The PM2 Methodology provides:

  • A project governance structure
  • Process guidelines
  • Artefact templates
  • Guidelines for using artefacts
  • A set of effective mindsets
  • Competences

The house of PM2 shows:

A foundation including Project Management Best Practices and The PM2 Methodology Guide. Build on this foundation we find four pillars representing:

  • Governance: 5 management layers: Appropriate Governance Body, Project Steering Committee (Directing layer: Project Owner, Solution Provider, Managing layer: Business Manager, Project Manager), Performance layer (Business Implementation Group, Project Core Team) and optional a Project Support Team.
  • Lifecycle (4 phases, 3 phase gates and approvals: Ready for Planning, Ready for Execution, Ready for Closing. Where needed: tailoring and customization and a structure to support agile teams)
  • Processes:
    • Initiating: Initiating meeting, project initiation request, business case, project charter
    • Planning: planning kick-off meeting, project handbook, project stakeholder matrix, outsourcing plan, project work plan, deliverables acceptance plan, transition plan, business implementation plan
    • Executing: executing kick-off meeting, project coordination, quality assurance, project reporting, information distribution
    • Monitoring & Control: monitoring project performance, control schedule, control cost, manage stakeholders, manage requirements, manage project change, manage risk, manage issues and decisions, manage quality, manage deliverables acceptance, manage transition, manage business implementation, manage outsourcing
    • Closing: project-end review meeting, lessons learned and post-project recommendations, project-end report, administrative closure.
  • Artefacts: requirements management plan, project change management plan, risk management plan, issue management plan, quality management plan, communication management plan, change log, risk log, issue log, and decision log.

The roof represents Effective (solutions & benefits) Delivery supported by Control & Agility and PM2 Mindsets (apply PM2, remain mindful, committed, deliver max. value, involvement, invest, become better, share knowledge, improve, inspiration).

In the appendix, we get:

  • Overview of commonly used PM tools & techniques: PESTEL analysis, make or buy analysis, stakeholder interest/influence matrix, risk likelihood/impact matrix, work breakdown structure, deliverables breakdown structure, effort and cost estimates, three-point estimating using PERT, project scheduling, resource levelling, Gantt charts, critical path method, critical chain method, earned value management, Pareto analysis, lessons learned.
  • PM2 and portfolio management model: Portfolio framework definition (Define portfolio characteristics and project categories, Define portfolio metrics, Define selection and reporting frequency, Define portfolio processes and governance bodies), Portfolio composition (Projects Identification, Projects evaluation, Projects capacity planning, Projects prioritization, authorization), Portfolio realization (Portfolio monitoring & control, Portfolio reporting, Portfolio change management, Portfolio benefit management, Portfolio optimization, Portfolio risk management) and Portfolio stakeholder management & communication
  • PM2 and Agile: Agile PM2 principles, extension with agile roles and responsibilities (agile core teams within the project core team), integration in the life cycle, and suggested agile artefacts
  • Ethics and conduct
  • Glossary

The Open PM2 initiative include:

  • PM2 guide – Open edition available through the EU Bookshop. For free see: PM2 guide
  • PM2 Methodology Wiki
  • PM2 certification exams
  • Project Support Network (PSN)


The PM2 guide is comprehensive, gives enough explanation for a complete picture of the traditional project management approach (in line with ISO21500, PRINCE2 and PMP) with a flavour of portfolio management and agile integration on the delivery level (PRINCE2 Agile offers much more) and includes benefits and transition management (comparable with MSP). The manual has a lot of colourful pictures, tables and references. Don’t confuse PM2 with the Japanese P2M (a guidebook for Project & Programme Management).

I assume that many people has put a lot of energy in developing this PM2 Methodology but I ask myself why do we need a new methodology, why spend a lot of money for something that is already available? Why a new certification program, why a new community? We have PMP, PRINCE2, PRINCE2 Agile, MSP and IPMA certifications we have best practice groups like BPUG and the IPMA community. What will be the added value of this new methodology paid by ourselves?

Lost in standards

Dia1In the last “projectie, edition 04-2014”, the bi-monthly magazine of ipma-nl, I published a Dutch article about the many methods and frameworks that are available in the field of portfolio, programme and project management. To download: Verdwaald in het standaardenbos IPMA Projectie magazine 04-2014 I created a sort of quick reference card with available standards and frameworks (It’s limited, there are many more). To download: standards-qrc-170129-v1-9

In the middle of the quick reference card you find a generic model with portfolio, programme and project management as horizontal boxes. Behind these boxes you will find vertical boxes with PMO, IT, benefits management, value management and risk management to support project, programme and portfolio management. And as the background I used two triangles representing the people and maturity of project, programme and portfolio management. From this model I made connections with several well-known organizations that develop and own standards. E.g. Axelos as the owner of PRINCE2, MSP, MoP, MoV, MoR, P3M3 and ITIL or PMI as the owner of PMBoK, The standard for Portfolio Management, The standard for Programme Management, OPM3, etc. You will also find AMPG, APM, IPMA and several suppliers of Agile/Scrum as well as some ISO models. dia1 In the Dutch article, I focus on the usage of these standards. It’s not that simple that you only have to select a project management method. Je must be aware that it will not be possible to implement all your ideas and ambitions. You have to select the right initiatives. This will ask for a portfolio management method. To realize your strategic objectives, you need more than only projects. You will run programmes too, asking for a programme management method. Besides temporary project and programme offices you probably need a permanent portfolio office as well as a centre of excellence to communicate, support and train staff to use these standards and best practices.

At a certain moment you want to know were you are from a maturity view, in comparison with others, and based on your own ambition you would like to know the gap you have to bridge. It will be beneficial for an organization if all these models or frameworks are connected to each other. As a rule of thumb, I would advice an organization to choose for either Axelos or PMI as the starting point and combine your choice with the competence baseline from IPMA. If you choose e.g. for PRINCE2, it makes sense to choose for MSP and MoP for your programme and portfolio management. For maturity scans you look at P3M3 because that’s in line with these standards. Your temporary and permanent PMO will be supported by P3O, etc. For supplementary techniques you could make use of the PMBoK from PMI.

Or, when you started with the PMI family, it makes sense to combine this with the project or programme board approaches from PRINCE2 and MSP and the usage of business cases as described in PRINCE2 9789401800068_CoverLR-541x850I am one of the authors of the book Global standards and publications, edition 2014/2015, Van Haren Publishing. You can download a free copy of this book. http://www.vanharen.net/file/PDF/9789401800068.pdf Please let me know if you are aware of new standards that are worthwhile to mention in this QRC.

for a comparison between PRINCE2 and PMBoK see the overview from KnowledgeTrain: Comparison PRINCE2/PMBoK


  • 17/01/29: Added PM2 Project Management Methodology from The European Commission
  • 17/01/29: Added Scrum @ Scale from Srcuminc.com
  • 16/01/23: Added Nexus (Scaled Professional Scrum) from Scrum.org
  • 15/10/04: IPMA ICB3 replaced with ICB4
  • 15/07/07: Added new Axelos framework PRINCE2 Agile
  • 15/05/27: Added Change mgt vertical + CMBoK (Change Management body of Knowledge) + CHAMPS2
  • 15/04/24: Added ISO 21500 project, 21503 programme, 21504 portfolio, 21505 Governance, 21506 Vocabulary
  • 15/02/24: Added CCPM (Goldratt), CMMi, Global Alliance for Project Performance Standards (GAPPS)
  • 14/10/21: Added Exin Agile Scrum from EXIN
  • 14/09/29: Added Agile Programme Management (Agile PgM) from APMG
  • 14/09/29: Added PRiSM™ (Projects integrating Sustainable Methods) from GPM
  • 14/09/29: Added Portfolio, Program & Project Sustainability Model (PSM3) from GPM