| Research | Community | Analysts | Teleconferences | Events | Consumer Data | Business Data | Executive Programs | Consulting | About Forrester |
| Primary Analyst Photo | Document Information | Rate this Document |
|---|---|---|
![]() |
December 31, 2009 Leverage PMO Skills To Build Program Management Competencywith Phil Murphy, Mary Gerush, David D'Silva |
|
This is an excerpt
Programs may spawn dozens or hundreds of projects, each of which accomplishes a unit of work that is meaningful to the business and may take guidance from a project management office (PMO). Programs are typically large and important enough to involve virtually every nontechnical business unit including legal, audit, and finance. By definition, they are so large that they require a multidisciplinary program office (PO). What is the difference between a PMO and a PO? If you are confused, you aren't alone. The differences between the two are significant, and applications professionals who don't define and govern them accordingly are missing an opportunity to fundamentally improve project and program success.
This is an excerpt
Price: US $499
Our Money-Back Guarantee: If you are not completely satisfied, return it for a full refund within three weeks of your online purchase.
Already a Forrester Client?
Log in to read this document.
Footer links (2 lists of links) |