Sign in
  • Blog
  • Processes
  • Project management
  • Skills
  • Training
  • P3M3

Author  Michelle Rowland – PRINCE2® and MSP® lead trainer, CITI

July 13, 2017 |

 5 min read

  • Blog
  • Processes
  • Project management
  • Skills
  • Training
  • P3M3

What’s the point of training people in project management best practices and then not using their new-found skills?

Clearly, there is no point; however, this seems to be an issue among organizations according to the latest AXELOS PPM Benchmark Study 2017 – The Value of Project Management Excellence.

P3M3® Maturity Model

This matters, as more mature organizations are less likely to experience project failure: almost 70% of mature organizations had avoided this in the past year, while only 47% of less mature companies had done so.

The project management training disconnect

Organizations are willing for people to go on project management training courses, which is laudable. Yet employers rarely offer a coherent introduction to what a project is before expecting their people to manage one. And new project managers often request their organizations to fund some form of training rather than it being automatically provided by their employer.

In the low maturity organizations, if someone has been on a project management course to follow a methodology that their manager doesn’t understand, the default position is to “crack on” with the project without following any form of the project method. This leads to a failure to embed new ways of working that staff bring back from training and ultimately means that nothing changes – including the organizational maturity level!

Investing in training but not in organizational processes means people won’t implement project management methods and their knowledge degrades. Without the encouragement to use the methods, an organization won’t have the repeatable processes that all project managers can follow; consequently, each project manager will waste time “reinventing the wheel”. This inconsistency at project level then affects prioritizing, monitoring and managing risk at the programme and portfolio levels.

The value of a PMO

The need for organizations to increase their project management maturity highlighted in AXELOS’ research points directly at the value of having a PMO (project management office).

Only 50% of organizations have a PMO, according to the research and this poses a problem: without a PMO – including a centre of excellence function setting and monitoring the use of methods and standards – you will get inconsistent application of those methods.

Without having repeatable processes embedded, you are setting projects up for failure as they will continue to repeat mistakes, take longer and cost more. And, in low maturity organizations that rely on external project management consultants, there is a high risk that valuable project learnings for the organization will walk out of the door at the end of the project. Having a PMO will ensure all learnings are passed on to improve future projects.

Equally, having a wider PMO (covering programmes and portfolios as well as projects) ensures there is strategic alignment within the organization. This is important so project managers understand how they are contributing to the organization’s overall goals and make a clear link between what they’re doing and what the organization wants to achieve.

A PMO involved at a strategic level is important to make difficult decisions about priorities, where investment should be directed and addressing the issues of tight timescales and budgets, as highlighted in the AXELOS study. Trying to do too much generally means everything grinds to a halt; making poor decisions about an organization’s capacity and capability to deliver is throwing good money after bad.

Project reviews – preventative medicine for project failure?

Another plus point for having a PMO is the discipline it can bring to conducting project reviews. As AXELOS’ study has revealed, those who conduct project reviews “always or most of the time” are less likely to experience subsequent project failure than those who review either “rarely or never”.

As my project management compatriot, Duncan Wade, has commented, “Lessons learned have been one of the holy grails of project management from the very beginnings of good practice and standards. And we are rubbish at them.” This tends to happen because lessons learned aren’t captured along the way and, by the final meeting at the end of the project, many learnings have been forgotten.

Project managers’ reviews are clearly important to have. However, it’s also worth having independent reviews by a centre of excellence to ensure a project is on track, strategically aligned, delivering what it should and that it’s well-managed and governed. PRINCE2®’s quality assurance approach includes an independent review of the project team which gives stakeholders greater confidence in the team’s project management performance. This also contributes to learning from experience, driving continual improvement.

If a project is going badly, without a review you won’t learn from it. Lessons need to be recorded, acted upon and embedded into ways of working that become repeatable in the organization. When necessary, changing the way you operate means the same mistakes won’t be made again and this – along with repeating the methods that have been successful – is a better building block for future project success.

For more information, see AXELOS' PPM Benchmark Study 2017.

Read more AXELOS Blog Posts by Michelle Rowland

MSP® Practitioner exam tips and advice

PRINCE2 Agile for Practitioners - How Using Agile Will Help Support the PRINCE2® Principles

Most common questions from PRINCE2® Foundation training - Chapters 1-6

Most common questions from PRINCE2® Foundation training - Chapters 7-10

Most common questions from PRINCE2® Foundation training - Chapters 11-18