2. 1 Change Management

3. 2 Changes to the Project Plan n Changes are a fact of life & a potential source of disaster ä Who authorises changes? ä Who pays for them? ä What about the knock on effects? ä How do you ensure that late changes are reflected in the documentation? ä How do you make sure your project does not change course?

4. 3 Controlling Change n A clear change plan specifying who can request/authorise changes n A procedure for evaluating and costing changes n A procedure for documenting changes n A change control plan is a standard part of project management documentation

5. 4 Change Management Plan n Change Request n Change Specification n Change Analysis n Costing & feasibility n Change decision n Change implementation & documentation

6. 5 And the downside - n May be perceived as bureaucratic n Restricts responsiveness to user needs n Emphasises costs and control rather than user needs

7. 6 Different Types of Changes n Distinguish between minor changes which affect an aspect of the project n Major changes which can cause the whole project to change direction n What kind of factors might affect the whole project?

8. 7 Examples n What would be the implications of a change to the specification – extend the network to another 5 rooms on site? n What are the implications of using a different platform? n What are the implications of late requests for changes to the interface?

9. 8 Summary n This lecture looked at the requirement for a change plan and the problems of managing change n Hughes et al chapter 4