Change Management 24 th May 2019 Rosie Forrest Collections Systems Manager Imperial War Museums
Change Management24th May 2019
Rosie ForrestCollections Systems ManagerImperial War Museums
ITIL* defines the change management process this way:
The goal of the change management process is to ensure that standardized methods and procedures are used for efficient and prompt handling of all changes, in order to minimize the impact of change-related incidents upon service quality, and consequently improve the day-to-day operations of the organization.
from Wikipedia*ITIL: Information Technology Infrastructure Library
© IWM (Q 19733)
Why we have a CMS
Put data in a sensible place
Find it easily when we need it
So Adlib is perfect as it is?
© IWM (HU 128285)
Do you use Adlib Designer to make changes to your CMS?
© IWM (RAF-T 6406)
Museum
Thesaurus
People
Media
Conservation
EntryLocations
ExitMuseum
Thesaurus
People
Media
Conservation
EntryLocations
Exit
Web API
Library
Museum
Thesaurus
People
Media
Conservation
EntryLocations
Exit
Web API
LibraryArchive
Museum
Thesaurus
People
Media
Conservation
EntryLocations
Exit
Web API
LibraryArchive
Illustration only – not accurate system diagram!
Museum
Thesaurus
People
Media
Conservation
EntryLocations
Exit
Web API
LibraryArchive
DAMS
Museum
Thesaurus
People
Media
Conservation
EntryLocations
Exit
Web API
LibraryArchive
DAMS
Axiell Move
Museum
Thesaurus
People
Media
Conservation
EntryLocations
Exit
Web API
Library
Archive
DAMS
Axiell Move
Museum
Thesaurus
People
Media
Conservation
EntryLocations
Exit
Web API
Library
Archive
DAMS
Axiell Move
Illustration only – not accurate system diagram!
Museum
Thesaurus
People
Media
Conservation
EntryLocations
Exit
Web API
Library
Archive
DAMS
Axiell Move
Museum
Thesaurus
People
Media
Conservation
EntryLocations
Exit
Web API
Library
Archive
DAMS
Axiell Move
Museum
Thesaurus
People
Media
Conservation
EntryLocations
Exit
Web API
Library
Archive
DAMS
Axiell Move
Museum
Thesaurus
People
Media
Conservation
EntryLocations
Exit
Web API
Library
Archive
DAMS
Axiell Move
Illustration only – not accurate system diagram!
Museum
Thesaurus
People
Media
Conservation
EntryLocations
Exit
Web API
Library
Archive
DAMS
Axiell Move
Stockphoto
Orders
Museum
Thesaurus
People
Media
Conservation
EntryLocations
Exit
Web API
Library
Archive
DAMS
Axiell Move
Stockphoto
Orders
Reports
Museum
Thesaurus
People
Media
Conservation
EntryLocations
Exit
Web API
Library
Archive
DAMS
Axiell Move
Stockphoto
Orders
Reports
Workflows
Rigs
Museum
Thesaurus
People
Media
Conservation
EntryLocations
Exit
Web API
Library
Archive
DAMS
Axiell Move
Stockphoto
Orders
Reports
Workflows
Rigs
Checks
Bookings
Museum
Thesaurus
People
Media
Conservation
EntryLocations
Exit
Web API
Library
Archive
DAMS
Axiell Move
Stockphoto
Orders
Reports
Workflows
Rigs
Checks
Bookings
Reports
Events
Museum
Thesaurus
People
Media
Conservation
EntryLocations
Exit
Web API
Library
Archive
DAMS
Axiell Move
Stockphoto
Orders
Reports
Workflows
Rigs
Checks
Bookings
Reports
Events
Illustration only – not accurate system diagram!
© IWM (Q 28625)
Howdo you keep
track of changes?
Deciding to make a change
Why do we need it?
Who is it for, and who will it affect?
Does this process belong in Adlib?
Am I solving a short-term problem
with a permanent change?
What could go wrong?
© IWM (Art.IWM ART LD 4140)
Objective Risk assessment Map dependencies/ compatibility Technical implementation plan Testing plan Backups – data and/ or system configuration Rollback plan Approval/ authorisation Training provision for users User release note or communication plan Log key details (what, why) in change tracker
© IWM (Art.IWM ART LD 1259)
Checklist for planning a change
Making smart changes
Beware changing existing system objects – do you know where it is being used?
Write a style guide for creating new system objects
Is this data already available somewhere else (merge/ FACS)
Could we adapt an existing function to support this requirement?
Change the look, not the function (screen change)
Use field/ screen conditions for a better user experience (conditions/ temporary fields)
Make the system clean the data (field/ storage ADAPL)
Transform data at export, instead of storing variations (XSLT)
Summary
Change is essential Make smart changes Log what you change and why you change it No change is insignificant Follow a change planning checklist, every time
Rosie ForrestCollections Systems ManagerImperial War Museums
© IWM (HU 99090)