Projects that focus on the needs of the customer generally have more successful outcomes than those that focus on the product itself. So the desire to keep a client happy is paramount to most project managers – they know that the client will have to sign-off on the completed project and if they are not satisfied with the end-result then the project will not be deemed a success.
But on the other hand a project manager also has to keep a tight grip on finances and the project schedule, which naturally means controlling requests for change. If the scope of the project starts to diverge substantially from the original requirements then the client may be happy with the end product but they will certainly not be happy with the budget and/or time over-run.
So how does a project manager put the client’s needs first when they want to change details of the project part-way through the schedule but still manage to deliver a quality product on budget, on time and within scope?
Project managers regularly face this challenge and their skills in managing people, budgets, schedules and deadlines are all vital at such times.
Clients do not always appreciate the consequences of a seemingly simple change. When a change is requested once the project is already in progress it can be much more costly to implement than if it had been built in at an earlier stage. Project plans usually have many tasks running in parallel and often have complicated inter-dependencies so any change can result in huge risk to the successful completion of the project.
But it would be naive to assume that change never happens in a project or that requested changes are always trivial to implement, which is, of course, why change management is considered such an important part of a project and the ultimate responsibility of the project manager. Project managers who are used to dealing face-to-face with clients know that it is simply not acceptable to turn down a change request without an extremely good reason that can be backed up with facts.
More usually the project managers will accept the change in order to show that they are cooperative and flexible and putting the clients needs first. But in order to mitigate the effect of the requested change they will need to have a good project management process in place simple project management software and the best project managers will often try and negotiate a compromise within the new request to reduce its impact on the whole project or trade off the new requirements with one of a lower priority that was already factored into the plan.
So what is the best way to implement a change control process?
Firstly, it is important that right from the start of the project everyone involved is aware that any change in requirements must be documented through a formal change request.
Every change request submitted should then be reviewed to ensure that those changes that are really necessary or desirable are actually approved. The purpose of the process is not to prevent change but to control it so that it does not jeopardise the success of the project. Requested changes are often the result of ideas that have arisen only as a result of seeing progress in a project in reality. Many people find it hard to think completely in the abstract or to relate fully to drawings, models or prototypes so it is important to recognise that many change requests will result in a better final product.