A04. Set up the PMIS

This activity is part of the Preparing section of the Project Flow. Preparation starts as soon as you have the idea or offer for the project, and ends with the decision to execute/accept the project, or drop it. Checking the feasibility or possible options for the project happens in this section as well.

Then the Project Manager sets up the PMIS (Project Management Information System). It’s a central place for technical, administrative, and managerial data and information in the project.

Use the following steps in this activity:

Create a folder or container for project files. It can be on an online storage (e.g. Dropbox, Google Drive, One Drive), or an internal server in your company.

Download the templates below, and add them to the folder.

Make sure there’s an automated system for saving daily backups.

It’s recommended to have a versioning system.

When using internal servers, it’s recommended to have a synchronized offline access to the files.

When using internal servers, it’s recommended to have a VPN server for remote access.

Give read/write access to appropriate stakeholders.

The following are the PMIS elements. The way they are used is explained in related activities.

Remember the following about all PMIS elements:

They are all about your perspective to the project; e.g. the Business Case is about the justification of the project for you, rather than the external customer.

Keep everything simple, clear, and in plain language.

Remember that adding more detail to the documents is not necessarily useful; it may be counter productive.

Project Summary

Project Summary is a simple text file that provides the high-level information of the project, including its goal, targets (cost and time), roles, etc.

Business Case

The Business Case is a text file that explains the justification of the project, and major risks that can affect the justification, as well as information on how to measure benefits during, and after the project.

Configuration Map

Configuration Map is a mind-map that shows the composition of the product, with acceptance criteria and status. It’s used to create a product-based understanding for the project.

The highest level of the mind-map is the final product of the project. Then it’s broken down into its main functional parts, each part into smaller building blocks, and so on. Make sure you’re not using organizational departments or functional units as a basis for the break-down. This concept is the same as a well-formed WBS (Work Breakdown Structure), or a PBS (Product Breakdown Structure).

You may have the temptation to ignore creating a mind-map of the Configuration and directly create it as a WBS in the scheduling software. This is unacceptable in P3.express, as using the scheduling software for this purpose will generate an activity-based point of view.

No template is needed for this element.

Project Files Directory

The Project Files Directory is a hierarchical set of directories/folders that will be used to store all project files (technical, administrative, etc). The hierarchy is a replicate of the Configuration Map, possibly with fewer levels. This helps you keep a product-based perspective throughout the project.

It’s best to use a template to name the files. The template doesn’t have to include too much information; it’s usually easier to add the information to the metadata.

No template is needed for this element.

Schedule Model

The Schedule Model is created in a project scheduling software (e.g. Microsoft Project), and contains the activities, and their information such as dependencies, duration, and cost. Its WBS (Work Breakdown Structure) is a replicate of the Configuration Map.

A high-level Schedule model is first created in the Preparation section, and then details will be added to the same model during Cycle Planning activities. The model may be adjusted in the Weekly Activities.

The model has two purposes: to provide the appropriate sequence of work, and to be used to measure progress, find deviations, and meet the targets by recovering fro those deviations.

No template is needed for this element.

Progress Register

The Progress Register is a spreadsheet that contains information on planned and actual performance data, and a simple dashboard for controlling the project.

Journal

Journal is a physical notebook, mobile application, etc. that the Project Manager uses to capture RIC (Risk, Issue, and Change Request) information immediately. The less important ones will be tracked in the Journal, while important ones will be moved to the RIC Register.

When selecting an application, make sure it’s easy for you to use it. More features, such as task management functionalities, can be helpful, but are not crucial. If you find them distracting, just use a simple note taking application.

No matter what you use for your Journal (physical notebook, mobile phone, tablet, etc), it should always be with you.

No template is needed for this element.

RIC Register

RIC Register is a spreadsheet that contains information about all Risks, Issues, and Change Requests, and well as their response plans.

Journal: a note taking software (unless you prefer to use a physical notebook)

You also need a storage for these, and also the Project Files Directory.

The following are suggestions for each of them.

Suggested Solutions for Storage

Online file hosting services. Team members can use the official clients of these services to create local, synchronized folders on their computers, and use the files more conveniently. They also provide version control, basic access control, and simple forms of backup. You still need to make external weekly backups manually, using third-party applications, or using scripts. The following are the major providers in this category:

Company’s servers, or an external hard-drive connected to the network. In this case, the following features should be made available for the storage:

Automatic Backups

Versioning

Access control

VPN, or another way of accessing the files from outside the company

A document management system or a system that covers document management, such as Alfresco or Sharepoint. It’s only recommended to those who already have such a system and prefer not to have parallel systems; otherwise, just use one of the first two simple options.

A sophisticated project management software that covers document management, such as Oracle and SAP solutions, or online ones like Basecamp. It’s only recommended to those who already have such a system and prefer not to have parallel systems; otherwise, just use one of the first two simple options.

Having project files distributed in project members’ computers without a centralized space is not acceptable.

If you don’t know which option is best, or you don’t have any preference, we suggest using a cloud storage.

Your choice here is not critical for small projects with simple schedule models. However, for larger or relatively complicated projects, it’s best to select a scheduling software that you’re most familiar with. Remember that your schedules are not supposed to be complex in P3.express; a chain is only as strong as its weakest link, and we usually have weaker domains in project management to take care of, instead of spending more effort on scheduling.

Suggested Note Taking Software

You can always use a simple physical notebook and a pen for the Journal, given that you have it with you all the time.

Having an application that is simple and easy to use is more important than having one with lots of fancy features. The whole point for a Journal is to open it quickly, and write down a RIC, before you forget it.

A simple file server in the company with required features + LibreOffice, LibrePlan, FreeMind, ToodleDo

Support

Setting up the PMIS is very easy. However, if you and other team members are not confident about it, you can simply ask help from your IT department to see which configuration is best. Try to have a conversation with them and go through all alternatives.