
Chapter 14: Project management
© EWP Go to www.emilewoolfpublishing.com for Q/As, Notes & Study Guides 385
- the project manager
- the project team members.
It should also specify the formal reporting procedures, the methods to be used
for monitoring and controlling the project, and the decision-making
responsibilities.
For example, the quality plan may specify that the progress on the project
should be monitored by a project assurance team (with named members) which
should meet regularly to consider progress reports from the project manager.
Project requirements. This section of the project quality plan specifies the
requirements for the project, in terms of what must be delivered. The project
work may be divided into phases, with each phase ending when a recognisable
‘milestone’ is achieved. Target dates will be set for reaching each milestone. (The
new project may be introduced in stages.)
The project specifications might include performance specifications for the new
system or process, security specifications, the required standards and any legal
specifications.
The completed project will be tested against these specifications, to make sure
that they have been met successfully.
Project development. This section of the quality plan specifies the methods to be
used to develop the new system, and the testing requirements. The different
phases of the development work should be identified, with target completion
dates for each phase.
Quality assurance. This section of the plan specifies how the work on the project
should be reviewed as it progresses, to ensure that it is being performed to the
required standards and specifications. The methods that will be used to carry
out quality assurance checks should be specified.
Change control management. This is concerned with requests for changes to the
detailed specifications for the IS/IT system as the project progresses. When
changes are requested, there should be a formal system for documenting the
requests – including the reason why the change is needed and why it is
desirable. There should be a system for approving requests for changes, and for
ensuring that they are made correctly (with suitable changes to all system
specifications and programming documentation, and suitable testing to make
sure that the change has been made correctly).
Testing methods. The quality plan should specify the testing methods to be
used on the new system or process before it is implemented.
Documentation standards. A section of the quality plan should specify the
documentation that should be produced for the new system or process. For
example, the requirements specification for a project might be drawn up using a
standard format in order to ensure that nothing is omitted from the statement of
requirements and that the requirements should be comprehensible.
Procurement. A section in the quality plan should specify quality standards for
the procurement of materials (and in the case of IS/IT development projects)
hardware and any off-the-shelf software. For example, the quality plan should
state that a specified Invitation to Tender procedure must be followed for the
procurement of major hardware items such as computer equipment and
communications link rentals.