Blog

This is an overview of the Issues I raise for the PRINCE2 2017 edition by Axelos. ...

AXELOS published the 2017 Edition of PRINCE2. Here is a verdict: is the 2017 edition an improvement? Why or why not? ...

The PRINCE2 2017 edition contains many issues. More than ever, it seems to be largely written from a wrong perspective and as a result it often deviates from the own principles. For many years (IT) suppliers tried to pretend they used and even trained PRINCE2. But in their cases, it only resulted in the very ineffective PINO (PRINCE In Name Only). In the 2017 version, they now ...

Many projects struggle with (external) dependencies. Most of the time these dependencies can not be managed. They are simply out of the control of the project and the project management is only able to monitor and maybe influence. There are however often dependencies that are results of poor project design and therefor occur by choice. These are dependencies between projects (in programmes and in portfolios) and should often be managed by focus on quality.

AXELOS has published an extension of PRINCE2: PRINCE2 Agile. Many think they are two polar opposites, PRINCE2 - symbolizing control, accountability, order – and agile – symbolizing self-organization and equality. And they are polar opposites. But for very different reasons. They are opposites because real, proper PRINCE2 is very agile and the Agile movement is based on old-fashioned ineffective Command and Control.

In a LinkedIn discussion about my paper about PRINCE2 and the Waterfall approach I received the following response that I would like to discuss here.

The LinkedIn response showed a lack of understanding on several levels of PRINCE2, but was unfortunately very common.