Infocouncil Projects
|
This
document is a preliminary guide to the approach and steps involved in
implementing Infocouncil at councils.
Management Plan
Project Management Personnel
The client organisation appoints a Client Manager and the
supplier organisation appoints a Project Manager. These people assume
responsibility for all deliverables attributed to their respective
organisations.
Risk Management
Key risks associated with the project are identified, and any
actions required to address these risks. If necessary a contingency plan
is prepared as part of the implementation.
Facilities
|
Allocation of responsibility for provision of facilities.
This usually involves 2 scenarios;
- Test Environment
- Live Environment
|
Equipment, premises, and licensing are identified and
itemised. Personnel details fall into subsequent parts of the project plan.
Change Requests
The procedure for identifying and scoping changes is set out.
A 'change request' form indicating cost and impact on delivery is required to be
signed by both managers before authorisation is given.
Errors
This is like managing change requests except costing is not
required. An 'error' form is used to register the matter. If deliverables are
affected in any way, the Client Manager is involved.
Client Reviews
Itemisation of documents for review and acceptance by the
Client Manager. The following is a typical list:
- User requirement specification
- Change request register
- Error register
|
Quality Plan
Personnel
Personnel are drawn from the client organisation for
acceptance testing. They are named with the particular functions or modules they
are responsible for.
The supplier organisation appoints personnel for programmer
testing and system testing.
Quality Sources
The following documents are used to inform the testing
process:
- User requirement specification
- User guides
- Training manuals
- Change request register
- Error register
|
Quality Procedures
The client organisation is responsible for using the quality
sources to acceptance test the software. Errors are logged and fed back to the
supplier organisation for action.
The supplier organisation is responsible for carrying out
internal testing. This is done in two rounds; programmer testing and system
testing. Errors are logged and fed back to the development team.
Development Plan
Personnel
The client organisation will be asked to provide personnel
for input into the user spec, review of the user spec and early software
walk-throughs. These are usually the same people that are appointed to perform
the testing.
The supplier organisation appoints personnel to create the
templates and configure the software.
Development Sources
The following items are referred to in the development
process:
- user requirement specification
- change request register
- error register
|
Development Deliverables
These are the deliverables:
- The software
- The user guides
- The training manuals
|
Implementation Plan
Personnel
The client organisation provides the personnel who are going
to use the system (end users) and those who are going to provide end user
support (key users).
The supplier organisation provides personnel for training,
installation and support.
Implementation Procedures
The following items need to be considered in the
implementation plan:
- Data preparation
- Training needs
- Office procedures in use of the system
- Support infrastructure
- Contingency plan
|
|