The following extracts
are from the Sanders Jones Project Initiation Document and
explain how an abbreviated version of the widely accepted
PRINCE2 methodology (PRojects IN a Controlled Environment
version 2) is used to deliver IT projects on-time and within
budget.
Implementation
Plan
The implementation plan is drawn up by the SJS Project Manager;
presented at the Project Launch Meeting and is used throughout
the project to ensure that all objectives are met.
Project
Launch Meeting
The purpose of this meeting is to launch the Project in such
a way that all members of the Implementation Team clearly
understand what the goals of the project are, and how they
will be achieved. The following points are normally covered
in the meeting:
Project
Meetings
The purpose of the Project Meetings is to keep all interested
parties fully informed of progress of the Project.
The frequency and content
of Project meetings will depend on the size of the implementation
and the requirements of the Client, but as a guide, internal
meetings should be held each week and full project meetings,
where SJS Personnel attend, should be held each month.
Prototyping
The aim of the prototyping sessions is to allow each element
of the business process to be checked with the software solution
prior to taking data on and using it.
In effect prototyping is the
dual running of the new Access Accounts system in parallel
with the existing system to allow the new methods and procedures
to be verified in advance of live running.
User
Training Guides
The outcome from the Prototyping sessions is an Operational
Manual that documents all of the key business processes.
User
Training
In order to simplify and speed up the training process users
are only trained on what they want the new system to do. The
operational manual provides the material for this stage of
the project.
Go-live
Support
Standard with the Sanders Jones project planning is to have
SJS people on your site(s) during the initial go-live and
at the first month-end for the new system. |