Document Controls

  • View a Print Friendly version of this document

    Print
  • Toggle highlighting of search terms in this document

  • Text Size: 

    • A (normal)
    • A (larger)
    • A (largest)

For Application Development & Delivery Professionals

Primary Analyst Photo Document Information Rate this Document

December 31, 2009

Leverage PMO Skills To Build Program Management Competency

by Margo Visitacion

with Phil Murphy, Mary Gerush, David D'Silva

Average:
(2 ratings)

This is an excerpt

Executive Summary

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.

Keywords

This is an excerpt

Buy Risk-Free

Price: US $499

Our Service Guarantee: If you are not completely satisfied with this document, notify Forrester within 24 hours of purchase for a full refund.

Already a Forrester Client?
Log in to read this document.

Add to cart

Save and Share

Document Tools

Spread the word:

RESEARCH CATEGORIES

Analyst

Margo Visitacion

Technology

IT Management, Portfolio Management & PMOs

Geography

Asia Pacific, Europe, North America