Going live? The highs and lows of getting a project into service Ciaran Talbot @ciaran_talbot Library Systems Manager The University of Manchester Library

A little context

Build CC BY 2.0 Image courtesy of Bill Ward on Flickr https://www.flickr.com/photos/billward/3413627084/

Run CC BY 2.0 Image courtesy of Mike on Flickr https://www.flickr.com/photos/pmiaki/4371642740/

Build it Run it

Project Service This bit

A B C Alma BookedIn CheckOut

The Alma implementation project

The Alma implementation project Project size: pretty big Drivers: consolidation, rationalisation

The Alma implementation project Live data migration Final “cutover” migration Test data migration Staff training Full launch Jan ‘13 Feb March Apr May Jun Jul Aug Sep Oct Nov Project Service?

How did the transition go? What went well? Data migration Devolvement

How did the transition go? What did not go so well? Staff user expectations

How do we evaluate the effectiveness of transitions?

How did the transition go? What did not go so well? Staff user expectations Unexpected consequences

The Alma implementation project But, not enough here Go Live Too much concentration here Project Service

BookedIn

BookedIn Project size: medium, collaboration Drivers: innovation, trying something different

BookedIn Project Timeline Kick-off 5th June 2013 June July August September October Kick-Off Development Prototype launch Pilot with students November December January 2014 February Launch

BookedIn Project Timeline Launch January 2014 June July August September October Kick-Off Development Prototype launch Pilot with students November December January 2014 February Launch

BookedIn Project Timeline Slippage Prototype launch Pilot with students Launch Development Kick-Off June 2013 July August September October November December January 2014 February

BookedIn Project Timeline Slippier Prototype launch Pilot with students Launch Development Kick-Off Jun ‘13 Jul Aug Sep Oct Nov Dec Jan ‘14 Feb March Apr May Jun

BookedIn Project Timeline Reality Access to prototype Pilot with staff Pilot with students Mobile App launch Full Launch Development Kick-Off Jun ‘13 Jul Aug Sep Oct Nov Dec Jan ‘14 Feb March Apr May Jun Jul Aug Sep Oct Nov

The Iron Triangle Quality Cost Time Scope

The Iron Triangle Cost Time Quality Scope

The Iron Triangle Cost Quality Time Scope

How did the transition go? What went well? Collaboration Trying something a bit different

How did the transition go? What did not go so well? Project and support = same people The eternal pilot Did we transition?

CheckOut App

CheckOut App Project size: quite small Drivers: curiosity, disruption

CheckOut App

CheckOut App Quality Cost Time Scope

CheckOut App Cost Time Quality Scope

How did the transition go? What went well? Launching something pretty unique

How did the transition go? What did not go so well? Tech outpaces policy

Does this all matter? - ineffective transition = loss of confidence - the eternal pilot problem - the different support models for project and service - “stealth” deliverables can delay great ideas

The challenge faced by the Library professional CC BY-NC-SA 2.0 Image courtesy of Jameson Gagnepain on Flickr https://www.flickr.com/photos/jameson42/4209575299

3rd Party Supplier You are here Stakeholders Library Central IT

What can we do? - Clarity on the handover - Be clear on who will steer the service -Involve/engage users relevant parties early - challenge the procedures - Separation of build and run?

Central IT

Central IT

Central IT Build Run

Conclusion Project Service 3. But, to make this more effective 4. We should think about what to do here 1. We’re not bad at this Transition Project Service 5. Starting here! 2. Or this

Build it Run it Conclusion = happier people, happier service Effective transition = happier people, happier service

Potential bonus round Exit self-service machines? (CheckOut demo)

Thanks & questions @ciaran_talbot CC0 images sourced from Pixabay or Pexels