Evolution of a project information system



With 90 percent of a project manager's work being communication, providing stakeholders with timely information is crucial. When that need is met, the number of purely informational meetings can be vastly reduced during a project's life cycle, which ultimately improves the productivity of all involved.

The Avantis business unit of London, England-based Invensys PLC's Software Systems Division is responsible for the software development, sales and implementation of a suite of enterprise asset management (EAM) products. At any given time, the company can be managing up to 10 software development projects, all with aggressive timelines and significant resource constraints. To reduce project issues and improve overall perception of the project management function, the Burlington, Ont., Canada-based firm has developed an information exchange system.

A Clear Need

Avantis' project management office (PMO) was formed in early 2001 to manage all marketing and support-sponsored projects, establish and control all project management processes, guidelines and procedures, and act as a focal point for disseminating critical project information.

Prior to the PMO, communicating information was time-intensive and inconsistent. While an intranet-based system was available for storing documents of common interest, the system was used inconsistently, and there was little use outside of the development department.

Status reporting was accomplished via a combination of meetings—some daily, some weekly and some electronic. Depending on who attended these meetings, critical information was often missed by key stakeholders until it was too late to resolve a particular project issue. Key project issues were neglected, and the overall organization was unaware of the status of various projects being managed by the development department. These factors affected the PMO's credibility.

The Action Plan

In May 2001, the PMO began to develop a system to gather and update project information and asynchronously communicate information to stakeholders. Before a tool could be implemented, a set of procedures was required:

  • Functional managers ensured that project managers tracked and updated issues, actions and risks daily.
  • The PMO manager reviewed the issues, actions and risks at day's end and held a morning focus meeting with all project managers to assist with escalation wherever needed.

To support this process, a Microsoft Excel Workbook (named IAR.xls for Issues/Actions/Risks) was created. Project managers had to print their IAR.xls workbooks daily, and these files were stored in a centralized repository.

To provide effective asynchronous communication of project information, a standardized naming convention for all key project documents and a standard storage and retrieval scheme were required. The project charter, the scope definition document, the schedule, the project organization chart and the project IAR.xls file had to be readily accessible. Once a project was completed, the sign-off document and the lessons-learned document also had to be stored in this standard location.


Figure 1. The data model for Avantis' project database is shown. This data model captures the relationships between the different entities that make up a project: actions, issues, risks, log entries and the project itself. It also captures the relationship between projects, people and programs.

Last, senior management needed a project portfolio health dashboard. A Microsoft Excel Workbook was created to graphically depict the “health” of a project by taking the weighted sum of quantitative project indicators, such as schedule variance, issues, risks and product defects. This health value was compared against thresholds to determine a color for the project. Project managers were responsible for daily updating of the data corresponding to their projects.

Once these procedures were established and the supporting tools were implemented, the organization's overall knowledge of the state of projects immediately improved. Directors of other departments began looking at the status information for the projects impacting their departments. On at least two separate occasions, critical risks that would have been missed until a subsequent senior management review meeting were promptly addressed.

Before, projects completed on schedule seemed to do so more as a result of last-minute heroics than any sustained planning. Since introduction of the procedures, every project that has been formally chartered has been delivered on schedule and met the defined expectations.

System Modifications

The system succeeded after a month of use, but two concerns surfaced:

  • By storing issues, actions and risks within a file-based system, the state-change nature of these items wasn't addressed. For example, an action could remain “open” beyond the estimated date of completion without any automated notification to the owner.
  • Ad hoc reporting of project information was difficult. For example, creating a report of all actions opened and closed within the last month was impossible without a significant amount of manual cut-and-paste operations.

For a truly robust system, the data had to reside within a relational database with forms-based input and ad hoc reporting capabilities. Ideally, by coupling a workflow engine with the database, it would provide state change capabilities for the issues, actions and risks.

For this next step in the evolution of the project information system, a data model design (Figure 1) was created. By utilizing a commercial relational database to store the structures and data related to these relationships, the concurrency control and referential integrity of a relational database could be leveraged.

Since commercially available project management tools didn't satisfy the requirements, the firm decided to build the system internally. The functional requirements and data model lent themselves to almost any commonly available commercial relational database management system. In addition, the simplicity of the data model and the basic functionality of this database allowed for quick implementation. PM

Kiron D. Bondale, PMP, is the manager of the Invensys-Avantis PMO. He has more than 10 years of experience with IT projects, which has provided him with ample first-hand experience of the importance of communication on projects.

PM NETWORK | APRIL 2002 | www.pmi.org



Related Content

  • Project Management Journal

    Major Knowledge Diffusion Paths of Megaproject Management member content locked

    By Wu, Hengqin | Xue, Xiaolong | Zhao, Zebin | Wang, Zeyu | Shen, Qiping | Luo, Xiaowei This article integrates social network analysis and main path analysis to investigate progress in megaproject management (MPM) from the perspective of knowledge diffusion. After measuring three…

  • PM Network

    In the Rearview Mirror member content open

    By Rockwood, Kate After a long haul, project managers and team members might feel the urge to wrap things up so they can move on to the next big thing. But giving short shrift to the debriefing process could…

  • PM Network

    Delivering the Wow Factor member content open

    By Simonsen, Amber Your most recent project came in on time, on budget and within scope—and stakeholders were satisfied. But something still seemed missing—you have a gnawing notion that your project checked a box…

  • Project Management Journal

    Influence of Communication on Client Satisfaction in Information System Projects member content locked

    By Diegmann, Phil | Basten, Dirk | Pankratz, Oleg This study illuminates the role of client-vendor communication in relation to project performance and client satisfaction in information system projects. Results from a field study with managers on…

  • PM Network

    Keep Your Guard Up member content open

    By Robinson, Andrew Way back in 1970, David Crosby lamented in a song of the times about how, in a moment of weakness, he almost cut his hair. I can relate. Letting down my guard as COO almost led to regret. I recently…