PM Earth

Structure Project Management

03 March 2009


Structure. For data to be accessible, it is most valuable that it be stored in a structured format. A well-designed data structure allows for accurate, easy access to all appropriate information. A poorly designed data structure may work for limited purposes, but leads to costly challenges down the road when a new question is asked that the data could answer, but the data is not organized in a way that allows the right information to be extracted.


Technical. The technical requirements for a database are similar to the technical requirements for other software. The database must interact with operating systems, networks, and online project management software that are currently in use or will come into use.

The database execution plan is developed in the four steps shown:

1. Define Database Requirements

2. Evaluate Existing Internal Databases

3. Evaluate Relevant External Databases

4. Prepare Database Adoption Schedule


Define database requirements. The first step is to define the requirements of a database that will meet the project management life cycle needs of the organization. Requirements are defined for each of the four aspects of a database. That is, there are content requirements, functional requirements, structural requirements, and technical requirements.


Evaluate existing internal databases. All internal systems that hold project management information – whether paper-based or electronic – are evaluated. A gap analysis is performed against the database requirements, and an approach to the modification and support, or the decommissioning, of the database is defined.


Evaluate relevant external databases. Database systems from sources, including vendors and freeware sources, are evaluated to determine if they will be part of the project management information system (PMIS) solution.


Prepare database adoption schedule. An approach to database implementation and a milestone chart are developed.


Copyright © Method123 Ltd 2000-2018