The Four Archetypes of the PMO |
||||||||||||||||||||||||||||||||||||
|
|
Home > Articles >
As I have assumed responsibility for gantthead's Program Management Office department, I have tried to raise some of the fundamental challenges and issues that face the typical PMO in an organizational context. While admittedly theoretical in some regards, the first few columns have endeavoured to lay the groundwork for a more involved discussion of developing PMOs. This column continues a multi-part series that addresses the practical steps and considerations in setting up a PMO in today's organizations.
For many of us who are assigned responsibility for developing a Project Management Office, one of the greatest struggles is the identification of a model that we can adopt as a framework for our development activities. The utmost challenge in this regard is the sheer diversity of frameworks that have been adopted in implementing PMOs in organizations. While previous columns have discussed specific dimensions that drive the diversity, my company's recent research work has led to the realization that there are several archetypes or scenarios that define the majority of PMO frameworks. Please login/register to read the entire article.
sponsored announcements and special offers
Difficult for competitors to equal. EMA reviews IBM Rational's new quality & requirements management offerings. The verdict, "For companies seeking to improve ROI delivered by software projects,we believe Rational's value proposition is difficult to match."
Microsoft Project Conference 2000
Use WorkLenz PPM to Manage Agile Software Development
|
| ||||||||||||||||||||||||||||||||||