What is a Project Management Office

1
What is aProject Management Office?
2
PMBOK 2000

• Section 2.3.4 Project Office
• There is a range of uses for what constitutes a
  project office. A project office may operate on a
  continuum from providing support functions to
  project managers in the form of training,
  software, templates, etc. to actually being
  responsible for the results of the project.

3
A Case Study

• Compuware ProjectOffice

4
The Business Reasons...
5
Foundation

• What goes into making a Project Management Office
  (PMO)?
• Define objectives
• Establish management
• Create an ongoing entity

6
Foundation

• Define objectives
• Sales Support
• Project Costing
• Repository of Information
• Methodology

7
Example Sales Support

• Developed sales support templates and processes
• Provided sales support services
• Expanded services as requested

8
Foundation

• Establish management
• Project Board
• Project Manager
• Infrastructure Leads

9
The PROJECTOFFICE Model
10
Foundation

• Create an ongoing entity
• Knowledge transfer, fast learning curve
• Talented PMs and writers, proficient in many
  tools and techniques

11
Preview of 2000 Goals

• ProjectOffice timeline

12
(No Transcript)
13
Sales Support Goals

• Provide expanded service
• Plan for growth (20)
• Continue support of SRC

14
Project Costing Goals

• Phase 1
• Implementation April 1, 2000
• Phase 2
• Project-level report for PMs
• Estimating or budgeting tool

15
Project Costing Goals

• Phase 3
• Review dashboard reports
• Web enable project costing
• Include all projects
• Provide remote access

16
Project Costing Goals

• Phase 4
• Develop trending reports
• Import additional data from BOS

17
Business Benefits

• Identify business trends
• Identify win/loss trends by client
• Identify Compuware presence at each client
• Track sales activity
• Target sales activity
• Track profitability

18
Repository of Information Goals

• Periodic updates to keep high level of interest
  in the site
• Additional functionality related to project
  information (e.g., store proposals, SOWs)
• Issue security of confidential information

19
Methodology Goals

• Train on industry standard practices (PMBOK)
• Emphasis on business QA
• Review proposal content for accuracy and
  consistency
• Establish branch-wide QA procedures (risk
  mitigation)
• Project reviews

20

• Thank you!
• Any questions?