|
As described in the overall FITS implementation
approach, we recommend a cyclic approach to
implementing new processes. Start small and
build upon sold foundations.
|
see FITS introduction
|
|
FITS Change Management is for people with little
free time to spend on implementing processes
and procedures and whose day-to-day activities
are unpredictable and must take priority.
Our aim is to help you begin to remove some of
the unpredictability by introducing best-practice
processes in small steps and so begin to realise
the benefits as quickly as possible.
|
|
|
Long-term scope
|
Ultimately, Change Management should apply to all changes, from
those affecting all or many users such as a server upgrade, to
small individual changes, such as installing an application on a
single computer. This ensures that there is a consistent
mechanism for keeping inventory records up to date. This aspect
of best practice is covered in more detail in the Configuration
Management section.
Applying the disciplines of Change Management to all changes
also encourages consistent and rigorous planning so reduces the
likelihood of incidents following a change. However, to implement
Change Management to this extent is time consuming.
|
|
Short-term
scope
|
In the short term it is advisable to start in a small and manageable
way and build gradually on solid foundations. We recommend that
in the first instance you apply Change Management only to major
changes that affect more than one user, such as the installation or
upgrade of a server or a change to the network configuration. For
this reason we have covered the handling of individual user
requests in Incident Management. We also recommend that you
approve requests for change as required and avoid the need for a
change advisory committee at least at first.
The implementation guide will take you through the steps required
to introduce Change Management in your school.
|
|
|
|
|
|
|
|
|
