System Page

Introduction

The concept of the project log is simple.
This means you have the incentive to find the time to maintain it.
It is powerful enough to be of real value.
So what is a project log ?
Basically it is a set of five overlapping structured documents called logs.
The logs contain similiar types of information but for different reasons.
The information redundancy helps to ensure that you avoid missing anything important.

Systems Log

The Systems Log defines and describes external factors relating to the project.
Interaction with stakeholders should also be recorded here.
The System Log should contain:

Functional Requirement Changes.

Large changes will probably refer to other documents which are driving the development
but it is particularly important to track the small verbal changes that often occur.

Environmental Changes.

This should include any change such as hardware, operating system, database and so on
that can have an impact on the project.

Installations And Rollouts.

Every time the product is installed or sent to a user during the development process it should be recorded.
Clearly this means that within Installations And Rollouts there should be a list of items
that come from Change, Defects and Ideas for cross reference to explain why a new installation has taken place.

The Logs are really a tool of delegation.
All that is really happening is the scope of the project is delegated to recording information into logs.
This is a useful tool when it is not appropriate to interupt the actual detail of the current task.

Introduction
Contents Anchor2
Contents Anchor3
Conclusion