Managing versus Directing: PRINCE2 2009

As I mentioned last week, the PRINCE2 project management methodology is currently undergoing a ‘refresh’ to make sure it fits the requirements of the marketplace. The new version, PRINCE2 2009, will be released on 16th June.

One of the major changes has been to slim down the PRINCE2 manual… by splitting it into two. The new version will have two different volumes, Managing Projects Using PRINCE2 and Directing Projects Using PRINCE2.

As you will have guessed, the two volumes are aimed at different users. Those of us who are project managers will be interested in the Managing manual, while senior managers and executives who will be involved at the project board level will be interested in the Directing manual.

Now, in a way I can see the sense of this split. The current PRINCE2 manual does talk about the various responsibilities and duties that project board members need to be aware of, but much of this information is buried amongst the nitty gritty of applying the methodology as a project manager. I can certainly understand that senior staff simply aren’t going to plough through a manual like that.

Indeed, I still think one of the most important things I do as a project manager is to sit down with senior management involved with the project and explain exactly how they fit into the project world – including how they need to hold me to account!

So I can see this splitting of the manual going one of two ways. It is possible that the Directing manual will start to be seen as vital reading for executives. Because they are involved in projects, they will work to make sure they understand their responsibilities, duties, and powers, and we as project managers will gain the benefit of informed and aware executives.

Or, of course, it could be that executives won’t pay a blind bit of notice to the Directing manual – without any qualification (yet) based on it, they may just not waste their precious time reading a rather dry text. Which would leave us as project managers buying both manuals, just so that we can again sit down with our project board and brief them on what they need to do in the project…

Maybe it’s the incorrigible cynic in me, but I rather suspect the second scenario is more likely. But at least we’ll know exactly where to find the information for our briefings…

What do you think? Do you think I’m being too cynical? Can you see other advantages to this split? Let me know!

Dansette