Infosphere's Project Management Framework
Outlined below is a summary of Infosphere's project planning approach. Larger jobs
require all these elements to be elaborated in great detail, while smaller jobs
can be expedited. This is a matter of judgement and negotiation with the client.
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.
Project reporting format and frequency are determined, as well as the policy for
handling changes in the specifications.
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
3 scenarios;
- development environment
- test environment
- live environment
Equipment, premises, and licensing are identified and itemised. Personnel details
fall into subsequent parts of the project plan.
Change Requests
If permitted, 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:
- project plan
- user requirement specification
- technical specification
- test specification and results
- project reports
- change request register
- error register
|
|
Quality Plan
Personnel
Personnel are drawn from the client organisation for acceptance testing. They are
named here with the particular functions or modules they are responsible for.
The supplier organisation appoints personnel for preparation of the test specification,
expected test results, programmer testing and system testing.
Quality Sources
The following documents are used to create the test specification:
- user requirement specification
- technical specification
- change request register
- error register
Quality Procedures
The client organisation is responsible for using the test specification to acceptance
test the software. Errors are logged and fed back to the supplier organisation for
action.
The supplier organisation is responsible for formulating the test specification
and carrying out internal testing. This is done in 2 rounds; programmer testing
and system testing. Errors are logged and fed back to the development team.
Development Plan
Personnel
The client organisation may 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 appointed to perform the testing.
The supplier organisation appoints personnel to create the technical specification
and write the software. A vital part of this is amending the specification to reflect
any changes occurring after commencement. On completion this becomes the Systems
Document for maintenance purposes.
Development Sources
The following items are referred to in the development process:
- user requirement specification
- technical specification
- change request register
- error register
Development Deliverables
There are 2 deliverables; the software and the technical specification.
Implementation Plan
Personnel
The client organisation provides the personnel who are going to use the system and
sometimes provides training resources. 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 (can be part of the development process if automatic conversion
involved)
- training needs
- office procedures in use of the system
- support infrastructure
- contingency plan
|