Andy Jordan is President of Roffensian Consulting S.A., a Roatan, Honduras-based management consulting firm with a comprehensive project management practice. Andy always appreciates feedback and discussion on the issues raised in his articles and can be reached at [email protected]. Andy's new book Risk Management for Project Driven Organizations is now available.
We hear a lot these days about monitoring project management compliance. PMOs are increasingly accountable for the way that projects are executed, and more than ever it’s not enough to deliver results--we have to deliver results in accordance with good governance and comply with PM standards.
Those standards are generally set by the organization through a PMO, but how do those standards get set and what should the standard be? This isn’t an easy question to answer, and too often there isn’t enough thought put into it. In this article I want to explore a few of the things to consider when establishing a model for project process compliance.
Identifying the standards
I can’t use this article to simply give you a bunch of metrics that you can use as project management standards within your organization--there are simply way too many variables. Some would argue that even within an organization it’s not possible to set meaningful standards as every project is different. However, as we all know, that’s not reality. PMs are expected to comply with the corporate standard and will (at least in part) be judged by their ability to do that.
That means that a lot of care and attention has to go into deciding what aspects of project management are going to be subjected to standards, as well as determining the quantifiable measure against that aspect.