Central Reporting: Independent or Undermined?
Last month's column introduced the challenge of how to create Project Management Offices of value, and specifically some of the critical success factors that distinguish exceptional PMOs. This month continues this theme through a more detailed exploration of what it takes to create a value-adding PMO, how to get there and why it makes sense to do so.
In the next few months we will explore the components that comprise effective PMOs, creating a detailed roadmap of both how to get there while avoiding the inevitable roadblocks and dead ends we will find along the way.
Probably the most common initial role of a PMO when first implemented is as a central focal point for status reporting within the organization. Even at this early stage, however, the seeds for success and failure are sown. The implications behind how and why a central status reporting capability is created are significant--beginning with the perceived value of centralizing this function within the organization.
The reasons for creating a centralized reporting capability fundamentally determine how it should be established. Is it to create a single repository for all projects? To create consistency of reporting and verify that status reports are actually being produced? To ensure objectivity of reporting and that the reported status reflects reality? Each of these reasons requires a different approach, with
Please log in or sign up below to read the rest of the article.
I hate asking for change. They always make a face. It's like asking them to donate a kidney.
- George Costanza