Upgrade to Pro — share decks privately, control downloads, hide ads and more …

From Bricks and Mortar to Virtual ITSM

Avatar for Dave Whyte Dave Whyte
February 19, 2018

From Bricks and Mortar to Virtual ITSM

This was presented at Pink18 in Florida on Feb 19th, 2018, it covers Auto Trader UK's 10+ years journey with ITIL and moving into the DevOps arena following a massive change in business culture, giving more control to the developers, working closely with Operations, improving release flow and overall success rate.

Avatar for Dave Whyte

Dave Whyte

February 19, 2018
Tweet

More Decks by Dave Whyte

Other Decks in Technology

Transcript

  1. Section title 2 From Bricks and Mortar to Virtual ITSM

    No ITSM Traditional ITSM Virtual ITSM AutoTrader Journey
  2. AutoTrader history timeline 4 1977 1995 UK national coverage of

    Auto Trader magazines 2007 Implements digital transition strategy Digital revenue = Print revenue 2010 Websites for Retailers Launches apps 2013 Closure of print magazines 2013 100% digital business in UK and Ireland Magazine Business 1996 Start of online operations - Launch of autotrader.co.uk Diversification Transition to Digital Fully Digital Business 1994 2007 2013
  3. 92% 4x 80% Of consumers know who we are and

    what we do in the UK Larger consumer audience compared to our nearest competitor Of UK car dealers advertise on Auto Trader 5 Stats that make us proud
  4. Section title 7 216 Physical Servers 3K Virtual Servers >

    4M Page Views / Hour > 250 Live Applications 2 x Data Centres 83 Releases / Week
  5. Section title 9 No business value Cut, cut, cut A

    mysterious black hole Print business
  6. Section title 11 Incidents not logged No trend analysis or

    event management Multiple high impacting, long lasting incidents No governance Preventable incidents
  7. Section title 12 Waterfall model Large bundled releases Slow turnarounds

    Lots of impact Regular back outs Operations an afterthought Not focused on quality
  8. Section title 13 Flawed change process Lack of governance New

    Change Manager CAB Good start, still painful
  9. Section title 16 Silos everywhere The ‘Goldfish Bowl’ Face of

    doom ‘That’s someone else’s problem’
  10. Section title 21 New toolset needed What did we want?

    Project to implement Set up Roll out Feedback Today
  11. Section title 22 CAB process change Opening up the barriers

    Flow overhaul Pragmatic solution Tedious & Frustrating, not AGILE Cumbersome change flow
  12. Section title 23 Release team Auto Deploy Failed release retro

    Powerful stats Opening up change windows
  13. Section title 24 Collaboration with resolving teams Out with the

    old! Incident Management Incidents being logged Problem Management contributed to Incident reduction
  14. Section title 25 Outside looking in Pain point visibility Root

    Cause analysis Trend analysis Major Incident reviews Tenacious action chasing
  15. Section title 26 Mature processes In a good place PinkSCAN

    audit Not a coincidence Circulate results to business Peter Hubbard Pink Elephant Head of Product Portfolio Biannual Audit Mutually beneficial relationship
  16. Section title 28 Operations still blockers Unorganised workflow Kanban &

    Stand-ups Long turnarounds Investing in the future
  17. Section title 31 MISSION: Most admired digital company in the

    UK Open plan & Transparent Bringing IT & the Business together Removal of contract army
  18. Squad Model Small, multi-disciplinary team Basedaround a Purpose Autonomous Led

    by Tech and Product experts https://labs.spotify.com/2014/03/27/spotify-engineering-culture-part-1/ Squad
  19. 34

  20. Section title 36 Private Cloud From Blocker to Enabler! ‘Fail

    Fast’, Learn Enabling Experimentation Shippr Facilitating ’Speed to Market’
  21. Section title 37 ‘Outside of the Box’ Still lots of

    graph overload Dev & Ops working together
  22. 41

  23. 42

  24. People – You need the right people to succeed, they

    need to be forward thinking, pragmatic, collaborate outside their sphere and show drive to challenge the normal. These people will help make changes to benefit all. Monitoring – I believe one of the main keys to dev/ops is shared monitoring, this gives one source of truth and a common language when discussing performance or stability. The Journey – To get to where we are today has taken a large investment in time and effort, there are NO short cuts, NO magic bullets. 43 Takeaways
  25. 44