PROJECT OVERVIEW (to download manual click here)

PROJECT

PROJECT tab

Any date can be entered – but Project Highway assumes for initial scheduling that tasks are based on a calendar that only allows Monday-Friday working and there are no holidays or non working periods accounted for. (These options can be changed when the data is exported into a project management software system at the end)

The PROJECT TOLERANCE is optional (but will be transferred into the Project Commander software – Microsoft Project has no facility for this)

Tolerances can be specified in % of periods of hours, days or weeks for TIME and % or amount for COST.

The default  library used for tasks is chosen here. If in doubt, leave as GENERAL.

PROJECT DEFINITION tab

If you wish to create a comprehensive PID (Project Initiation Document),  then there is a list of other sections you can complete (not all boxes need to be completed – some can be left blank).

When you click on an item, a text box opens – there is a paste icon to copy any text in from another document.  Click on the item to close the box.

If all the sections are filled in, then it would meet the full requirements of PRINCE2.

There are 2 reports that come out of the system ..

• A full PID (fully compatible with Prince 2005 & 2009)
• A Project Specification

All the items filled can be printed in a Project document at the end of the process. All Project Definition fields are included on the PID (whether they are empty or not). Only the Project Definition fields with text are included on the Project Specification.

PHASES

The project can be broken down into separate phases or just be displayed as a long task list by ignoring Phases.

In the GENERAL library, there are 3 sections with example phase headings underneath.

Phase descriptions can be dragged from the libraries or input manually into the left window by using the INSERT key or right  click on the left window.

REQUIREMENTS

This step is wholly optional. However, it does make you think about all aspects of what is required to be delivered and what the constraints are.

This section is made up of one line items. There are number of popular examples that can be dragged and dropped into the list and then edited or input manually.

QUALITY

This section is optional. You can paste any previous text direct into here along with your typed text. You may often simply refer to approved industry standards or other organisational Quality documents.

Even though this is optional – for business critical projects or customer projects – it is advisable that quality is addressed and documented clearly and comprehensively.

RISKS

This section is optional. Just like Requirements - this section is made up of one line items. There are number of popular examples that can be dragged and dropped into the list and then edited or input manually.

Even though this is optional – for business critical projects or customer projects – it is advisable that Risks should be identified and documented clearly and comprehensively.

GO TO PROJECT PLAN >>>