Project Governance - Multiple Projects + Clients

Patrick,

Firstly I would suggest that you don’t make any decisions about the project governance strategy alone.

Project Governance is just an extension of Corporate Governance into projects. The aim should be to align the accountability and decision making processes for each project within your programme of works.
Coming up with a common risk management approach and change control process can help ensure consistency with the sponsor (internal) and end clients. It also makes reporting easier for those who will be writing the reports (i.e planner) as there is a common standard.

What issues do you see as eroding the cost benefit of managing the work as a programme?
The alignments aim should be to help you achieve your strategic goal, be it company vision or just programme vision.

Oliver,

That is the intention but I thought I like to know what pitfalls that I might be facing in projects of this nature. In particular, how to protect the cost saving projection by combining them.

The issues I think I could be facing are:

1. Commercial-in-confidence might required separation of the same artifacts such as design and test documents;and
2. Managing end clients responsibilities such as requirement signoff so that design and development phases can start at the same time across all the projects.

Anything else?

Patrick,

I would have thought that commercial-in-confidence would have been covered by your companies corporate procedures regarding protectively marked work.

Obviously the project organisation will need to be aligned with the commercial / security needs of the project.

Procedures are the key in creating the correct intellectual property arrangements for the programme. Things such as partitioned drives for commercially sensitive / non-sensitive items such as designs and documents are effective in letting the relevant staff have the required access to information.

As for managing end client responsibilities, i’m sure your aware its all down to communication.

Responisibility assignment matrices- a cross section view of the WBS against the OBS, showing clear lines of responsibility for all stakeholders to sign on to. This can remove the risk of liability if delays occur, even in internally sponsored project.

Something i have recent experience of, co-working. If you envisage delays due to signoffs, then why not remove the delay by integrating the sign-off into the project office. This will benefit the customer just as much as you!

Oliver