MPMM Method123 Project Management Methodology

General Project Management Issues

24 March 2009

Key project management issues include:

n

Is the database essential to solve any of the most critical problems that the PMO is tasked to solve?

n

Can the PMO operate affordably before the new PMO database is in place?

n

How quickly, and at what cost, can the PMO create and deploy the new RDBMS?

n

Will imposing a whole new system and way of working rush change too fast, creating resistance?

The adoption schedule can either reflect the goal of having the new PMO RDBMS ready for the launch of the PMO execution phase, or specify that the new PMO RDBMS will be an enhancement to PMO services at a later date.

Here is an example of a statement of approach:

PMO Database Statement of Approach

3/1/2007

Question

Approach

How will existing data sets be handled?

Imported electronically, with as much historical data as can be conveniently converted.

How will existing data structures be handled?

Most will be discontinued when new system starts. Data structures in the financial and procurement databases will run in parallel with the new PMO RDBMS. This does mean some duplication of data, but is the only cost-effective solution that can be implemented this year.

Will the new PMO RDBMS be available when PMO execution begins and services are first launched?

Yes

What date will the PMO RDBMS be ready for use?

7/1/2007

Will the new RDBMS be based on an existing internal system, or acquired from an external source?

Acquired

What is the name of the source for the new PMO RDBMS?

Oracle® SQL Server

What will the name of the PMO RDBMS be?

IPIS (Integrated Project Information System)

Who is the project manager responsible for creating the PMO RDBMS?

PMO IT Lead

Who will perform the work of creating the PMO RDBMS? (PMO staff, IT staff, and/or outside consultants)

IT Staff – they handle all Oracle® implementation

How much historical data will be entered in the RDBMS?

Up to 3 years past data, where the data is in the same format as current data on this system.

Identify any other issues related to requirements or interfaces for this new database and the data it will contain.

Special tables will be created for low-speed networks (cellular) and handheld devices.

Once the Statement of Work is complete, a milestone chart of the key dates in the database adoption schedule can be developed. Coordinate the work to be done with available resources and the other PMO execution plans to create this schedule. Here is an example:

PMO Database Implementation Milestone Chart

3/1/2007

Item

Work start

Testing Start

Item Ready

Acquisition of RDBMS

4/1/2007

4/7/2007

4/15/2007

Entry of table definitions and relational structure

4/3/2007

4/7/2007

4/15/2007

Entry of test data

4/16/2007

4/20/2007

4/27/007

Creation of user interfaces

5/1/2007

5/10/2007

6/15/2007

Entry of actual data

6/10/2007

6/16/2007

6/20/2007

Final testing and changes

6/21/2007

6/21/2007

6/30/2007

Other items

n/a

n/a

n/a


 
 
Posted in General


Copyright © Method123 Ltd 2000-2012

 
Tips and Hints Archive
A Good Project Manager
or the Report Status Service
Service Features
Report Status Service
Management Software
Project Management Services
Risk Management
Execution Phase
All Tips and Hints
Categories
General (45)
Project Management Office (45)
Project Office (34)
PMO (38)

RSS FEED