April 2011 outline briefing for changing the organisations IT infrastructure.

1. Change Management Updating IT system having chosen preferred supplier. How will Transition project be managed? In house Or Bought in Internal briefing April 2011 DRAFT v1.1 Author: Michael Beckett

4. Trained?

5. Can Hardware cope?

7. Do we want to be reliant on a third party for this project?

8. Contracting out.

10. Experience: Research what problems others who made this transition encountered or what precautions they took.

11. Risk assess and 'common sense test' plans.

13. Set Realistic Goals

14. Advise Staff of Goals and time line

15. Reviewing plan and snagging contingencies

16. Expectation Management

17. Resilience, robust disaster recovery procedure

18. Public information – Celebratory press release

20. To IT staff telling them what is going to happen – informing them of up & coming training

21. Admin staff – Advantages of new system

22. Advise on training

24. Ensure Users trained before go live date so they can seamlessly cope with the change.

25. Internal Communications Strategy: Inform other staff of developments of progress.

27. Check before going live

28. Keep back up just in case of glitch

29. Get staff to try system before going live

31. Key staff for Day 1 5.30pm evening go live test.

32. Key staff for following morning 8.00am live review. In case of unresolvable system error able to roll back to previous system until 8.45am do or die A project deadline for Day 2.

33. Daily reviews at 5.15pm & 8.15am as required.

35. Report on projects 'Snagging list' monitoring identified issues and progress against expected time frame for resolution.