There are a number of key prerequisites for an effective PMO. Having the right sponsorship and remit are the most critical. Staffing the PMO with the right people – proactive experienced people with at least a smattering of delivery experience mixed with enthusiastic and technology literate less experienced staff is the second key to success. Third, and often either overlooked or not paid enough attention to is setting up the PMO controls framework the PMO is going to own and drive.
Project and programme managers like clarity, stability and minimal bureaucracy. A good controls framework delivers on all three fronts. A clear framework sets expectations and clearly explains why information is collected and how it is used. ‘No surprises” is the byword here.
So what does the controls framework cover? Here’s the shopping list:
- Process areas:
- Status reporting
- Risk, issue, assumption and dependency management
- Resource management
- Financial management and reporting
- Programme change control
- Infrastructure change control
- Communications management
- Tools and systems
- Document Library
- RAID Log repository
- Change Control Log(s) repository
- Planning tool(s)
- Key artifacts
- PMO Handbook
- Detailed process descriptions
- Programme Charter or Directive
The PMO Handbook is the bible here. It describes not only what each process, tool or system is, but why they exist and the data that is collected and analysed, and why.
Over the coming weeks I’ll blog more about some of the key elements of the controls framework and how the data is used. In the meantime, how does your PMO stack up against my model list? I’d really appreciate your feedback.