TABLE OF CONTENTS Once the users have accepted the system and started to use it, there are three main jobs to do: running the system, fixing errors, and making changes. Thus the production stage is a mixture of operational work, maintenance, and new developments.
Depending on the structure of your organisation, you may be responsible for some operational tasks, the users may do them themselves, or there may be a specialist production group. Whichever is the case, the aim will be to make sure that the users are kept properly informed, they have access when they need it, and their data (and the business processes dependent on it) are properly protected according to documented procedures.
Maintenance is essentially fixing errors in the production system, possibly combined with handling and assessing requests for change. However, it is important to keep the processes of error fixing and making changes separate, as otherwise the changes will tend to be uncontrolled. If you have responsibility for either or both of these processes you will either have to prepare the system for handing over to the maintainers, or create and sustain the right set of attitudes to keep maintenance effective and under control.
Changes should (strictly speaking) go through the whole development life-cycle. In practice, there will usually be an abbreviated version for smaller changes. Every change must be properly evaluated (for cost, including all its impacts, and benefit) and approved. Then, when approved, the documentation must be updated, in the proper order, before the change is...
