• Skip to main content
  • Skip to secondary menu
  • Skip to primary sidebar
  • Skip to footer
  • Home
  • About Mel Bost
  • About the Book
  • PMO
    • PMO Leadership
    • PMO Maturity
    • PMO Benchmarking
    • PMO Execution
  • Risk Management
  • SMART Goals
  • Project Information
    • Project Lessons Learned
    • Project Business Requirements
    • Project Communications
    • Project Community
    • Project Environment
    • Project Manager Qualities
  • Knowledge Management
  • Practices
    • Next Practices
    • Best Practices

Mel Bost - PMO Expert

PMO Expert

So How Do I Start a PMO?–Session I

January 25, 2010 by Mel Bost 1 Comment

Suppose you are a member of a successful IT or other business functional group whose members have successfully delivered “value” to their larger organizations/corporations through successful project implementation. Inevitably, this success brings additional requirements from the corporation to deliver more “value” through more projects over time. You begin to feel the pressure because resources may not be readily available or accessible in the timeframe you are asked to deliver, teams may not be prepared and, in general, although you saw it coming, your best efforts just to deliver the last increment of “value” was enough to keep you occupied.

So what’s a body to do?

This is exactly what faces every organization who decides to ramp up to a Program Management Office (PMO). But the question remains “how do I define just what I need in the timeframe I have been given to be successful?”

My answer which I have leveraged in several situations before is to take a blank sheet of paper and write a “funding authorization statement” for a single project just as if you were seeking funding today.

An example:

“This funding authorization seeks $37.5 million (capital and expense) from the IT Executive Board to deliver the IT Marketing Apps Development Project for new Stores by December 2011. The Business Case is defined as follows…..The economics and payback are defined as follows….The risks to the project completion are defined as follows…..The proposed project team will consist of the following from IT and/or functional business units. The external consultants proposed for this project are ………Authorization of this project is part of a larger portfolio of projects which have been addressed by the IT Executive Board in its meeting of August 21, 2009.”

Now, such a simple statement defines many things. It defines what project, what funding group, what business case, what risks, etc.

Every one of these details must be provided by resources which reside in the PMO or functional business units interfacing with the PMO.

When the PMO has a number of these Authorization Statments, it can begin to decide if a Methodology of handliing the Portfolio of projects and the LifeCycle of the Project Management Process needs revamping to facilitate consistency in the way all the projects are evaluated and authorized.

What does your “clean sheet of paper” look like? Have you given it some thought lately? If you are an organization looking to move to that next level of superior project service and “value addition” to your Corporation, think about that “blank sheet of paper.” Your business context will determine what elements need a place in the PMO and what must come from the business functional areas and perhaps even what must come from external stakeholders.

Filed Under: PMO

Reader Interactions

Trackbacks

  1. How To Build A PMO From The "Grass Roots Level" Using A Clean Sheet Of Paper says:
    June 1, 2010 at 12:07 am

    […] building a PMO from the “grass roots level”, which many of you will recognize from my previous posts as taking a clean sheet of paper as the starting […]

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Primary Sidebar

Search The Site

About Mel Bost

Mel Bost is a project management consultant specializing in project closeout and lessons learned, as well as process improvement, best practices, and benchmarking. For the past several years, he has been teaching “Project Management for Research” to postgraduate students at Arizona State University, as well as developing new approaches to the research process. Read More

Project Management Lessons Learned: A Continuous Process Improvement Framework

The NERS department congratulates C. Melvin Bost, Jr., on the publication of his new book.

Categories

Footer

Recent Posts

  • To My Project Community Readers:  Please Support the Fastest Path to Zero Initiative
  • The Role of Cognitive Sciences in Project Management and PMO Performance
  • A Tribute to Louis Tice: What He Contributed to my Thoughts about Project Management
  • How Can Project Managers Use the “Scientific Method” to Finesse Projects?
  • When is Project Management Much More Than Just Cost, Schedule, Scope and Quality?
  • The Importance of Perception in Capturing and Documenting Project Lessons Learned

Read the Book

Search the Site

© 2025 · Mel Bost, PMO Expert · Customized by Element Associates