Servicedesk and IT Support Show, London 2017
Audio from the presentation:
https://soundcloud.com/diversifieduk/sits-2017-is-devops-really-changing-it-support-jon-hall-bmc
Apidays New York 2024 - APIs in 2030: The Risk of Technological Sleepwalk by ...
Â
Is DevOps Really Changing IT Support?
1. Š Copyright 2017 BMC Software, Inc.
Is DevOps Really Changing IT Support?
Jon Hall
Principal Product Manager, BMC Remedy ITSM
Servicedesk and IT Support Show, London 2017
2. Š Copyright 2017 BMC Software, Inc.
@JonHall_
Enterprises are transforming around software
30% digital sales 80% digital sales
3. Š Copyright 2017 BMC Software, Inc.
@JonHall_
Case study: Global travel company
⢠1000+ applications
⢠5,500 employees
⢠3000 developers! (many are contractors)
⢠One servicedesk
4. Š Copyright 2017 BMC Software, Inc.
@JonHall_
â10+ Deploys per Day: Dev and
Ops Cooperation at Flickrâ
First DevOpsDays event
(Ghent, Belgium).
Publication of
âThe Phoenix Projectâ
âThe Lean Startupâ
âContinuous DeliveryâFirst USA DevOpsDays
20102009 20132008 2012 2014
Significant enterprise
adoptions
Brief history of DevOps â some key events
Patrick Debois and Andrew
Shafer form Agile Systems
Administration Group
âOps, DevOps and PaaS
(No-Ops) at Netflixâ
5. Š Copyright 2017 BMC Software, Inc.
@JonHall_
DevOps is going mainstream
DevOps Enterprise Summit speakers, 5th-6th May 2017, London
6. Š Copyright 2017 BMC Software, Inc.
@JonHall_
DevOps Outcomes: ITSM under pressure?
Deployment frequency:
Change lead time:
Mean time to recover:
Change failure rate:
46% better
440x faster
96x faster
5x lower
7. Š Copyright 2017 BMC Software, Inc.
@JonHall_
Enterprises are different
Software:
Customers:
Infrastructure:
Cadence:
Open source, cloud.
Emergent or transformed markets
Software defined & public cloud
Multiple daily releases.
Legacy on-premise + New cloud tools
Established consumer and B2B markets
On-premise, cloud transitioning.
Improving from traditional long cycles
8. Š Copyright 2017 BMC Software, Inc.
@JonHall_
âThe enterprise space doesnât move
slowly because theyâre stupid, or
they hate technology.
Itâs because they have users.â
âLuke Kanies, Founder, Puppet. Configuration Management Camp 2015, Belgium.
âŚand in particularâŚ
9. Š Copyright 2017 BMC Software, Inc.
@JonHall_
DevOps adoption in established enterprises
âStartup-likeâ
teams formed.
New products,
Ad-hoc support.
Enterprise ITSM âadoptsâ
frontline support.
10. Š Copyright 2017 BMC Software, Inc.
@JonHall_
Case Study: HP Laserjet Firmware team
10% code integration
20% detailed planning
25% porting code
25% supporting current product
15% manual testing
5% remaining innovation capacity
2% continuous integration
5% agile planning
15% one main branch
10% customer equipment branch
5% testing (most automated)
~40% capacity for innovation
20112008
(A well-cited example of enterprise DevOps transformation)
11. Š Copyright 2017 BMC Software, Inc.
@JonHall_
⢠Merged 24 codelines into a single build.
⢠Highly automated testing, including physical simulations
⢠âStop the lineâ if anyone breaks the build or the test suite.
⢠400-800 worldwide developers... âRemote Agileâ via ChatOps
Case Study: HP Laserjet Firmware transformation
12. Š Copyright 2017 BMC Software, Inc.
@JonHall_
Case Study: HP Laserjet Firmware transformation
⢠Support was fully merged into the
development process, on the same code-line.
⢠Prioritization is handled by a marketing lead
⢠Hence Support âticketsâ are effectively
managed completely in SDLC tools
⢠Customer context is key.
13. Š Copyright 2017 BMC Software, Inc.
@JonHall_
Case Study: A national mapping agency
Development Operations
Before DevOps transformation:
Application1 Application2
Support
14. Š Copyright 2017 BMC Software, Inc.
@JonHall_
Development
Operations
Team Leader
Support Specialist
Application1 Application2
Case Study: A national mapping agency
After DevOps Transformation:
15. Š Copyright 2017 BMC Software, Inc.
@JonHall_
Application1
Case Study: A national mapping agency
Identity
Manager Remedy
⢠New application teams.
⢠User assignment to teams.
⢠Inter-team moves.
⢠Roles within teams
(e.g. âincident managerâ).
⢠Foundation data updates
⢠Autonomy: Team leaders juggle the teams
⢠Some roles remain outside DevOps teams â e.g.
Problem Mangement
16. Š Copyright 2017 BMC Software, Inc.
@JonHall_
DevOps challenges ITSM orthodoxies
⢠âIncident Managementâ looks different
⢠Change Management struggling to show value.
⢠Release Management increasingly automated
⢠Cloud and Software Defined Infrastructure dominate.
⢠âTraditionalâ ITAM and CMDB less relevant.
17. Š Copyright 2017 BMC Software, Inc.
@JonHall_
Servicedesk challenges
⢠Application services suddenly appear
⢠No visibility of issues transferred to developers
⢠Lack of knowledge sharing
⢠New kinds of customer, especially external
18. Š Copyright 2017 BMC Software, Inc.
@JonHall_
Change Manager challenges
⢠Accountability but lack of visibility
⢠Some processes adapt poorly to DevOps. e.g. CAB
⢠Reduced currency to assert role
19. Š Copyright 2017 BMC Software, Inc.
@JonHall_
But... Enterprise reality challenges DevOps!
⢠Customer/business context of incoming issues and bugs.
⢠Adaptation to life âon callâ
⢠What to prioritise? Fix bugs or build new stuff?
⢠How to process alerts, particularly if noisy/low-quality.
20. Š Copyright 2017 BMC Software, Inc.
@JonHall_
âIT organizations that have tried to custom-
adjust current tools to meet DevOps
practices have a failure rate of 80%â
We need a rethink
DevOps and the Cost of Downtime: Fortune 1000 Best Practice Metrics Quantified (IDC, 2014)
21. Š Copyright 2017 BMC Software, Inc.
@JonHall_
⢠Work-in-progress queues
⢠Asynchronous communication
⢠Single role teams
⢠Individual over-exposure
⢠Poor knowledge transfer
How to annoy a DevOps advocate
22. Š Copyright 2017 BMC Software, Inc.
@JonHall_
LEVEL 2 SUPPORT LEVEL 2 SUPPORTLEVEL 2 SUPPORT
LEVEL 3 SPECIALISTS LEVEL 3 SPECIALISTS LEVEL 3 SPECIALISTS LEVEL 3 SPECIALISTS
LEVEL 1 SUPPORT
Classic âTieredâ Support Structure
23. Š Copyright 2017 BMC Software, Inc.
@JonHall_
LEVEL 2 SUPPORT LEVEL 2 SUPPORTLEVEL 2 SUPPORT
LEVEL 3 SPECIALISTS LEVEL 3 SPECIALISTS LEVEL 3 SPECIALISTS LEVEL 3 SPECIALISTS
LEVEL 1 SUPPORT
Escalation
Escalation
Classic âTieredâ Support Structure
24. Š Copyright 2017 BMC Software, Inc.
@JonHall_
LEVEL 2 SUPPORT LEVEL 2 SUPPORTLEVEL 2 SUPPORT
LEVEL 3 SPECIALISTS LEVEL 3 SPECIALISTS LEVEL 3 SPECIALISTS LEVEL 3 SPECIALISTS
LEVEL 1 SUPPORT
âŚwhen the answer is here⌠âŚor here.
Issues may spend time here
25. Š Copyright 2017 BMC Software, Inc.
@JonHall_
LEVEL 1 SUPPORT
LEVEL 2 SUPPORT
LEVEL 3 SPECIALISTS
When tickets
eventually escalateâŚ
âŚthey frequently
bounce back for
clarification
26. Š Copyright 2017 BMC Software, Inc.
@JonHall_
LEVEL 1 SUPPORT
LEVEL 2 SUPPORT
LEVEL 3 SPECIALISTS
LEVEL 1 SUPPORT
LEVEL 3 SPECIALISTS
LEVEL 2 SUPPORT
SUBJECT MATTER EXPERT
The system encourages âheroesâ (not in a good way)
27. Š Copyright 2017 BMC Software, Inc.
@JonHall_
Swarming â much better aligned to DevOps
Specialist Product Teams
Severity 1 Swarm
Dispatch Swarm
Prioritise
Backlog Swarm Backlog Swarm
28. Š Copyright 2017 BMC Software, Inc.
@JonHall_
⢠Autonomy (guidelines, not rules)
⢠Knowledge transfer and skills development
⢠ChatOps
⢠Reduces Work-in-Progress accumulation
⢠Protects individuals from burnout
Swarming â much better aligned to DevOps
29. Š Copyright 2017 BMC Software, Inc.
@JonHall_
âAt every step of the workflow, we have to
go into the ITSM tool and click somethingâ
âReally I want to work with chat, our
source control system, and email"
Tooling challenges
32. Š Copyright 2017 BMC Software, Inc.
@JonHall_
DevOps teams want to use the CMDB
âDrifts, timelinesâ
âThe person who is on call at
4am needs to know who has
been doing whatâ âContext is a trigger word for me...
in a company of 4000 people,
things can get out of hand really
fast if you don't have contextâ
âWhat is actually
running on an
environment?â
âIf you're dropped in the
middle of something,
how did you get here?"
(but not through the actual interface!)
33. Š Copyright 2017 BMC Software, Inc.
@JonHall_
⢠Customer and business context
⢠Service at scale
⢠Impact analysis and triage
⢠Knowledge Management
⢠CMDB
⢠EtcâŚ
ITSM can bring significant valueâŚ
34. Š Copyright 2017 BMC Software, Inc.
@JonHall_
⢠Learn from DevOps acheivements
⢠Observe and understand the culture
⢠Understand where value is added and where it isnât
⢠Bring that value to DevOps teamsâ tools⌠API all the things!
⢠Alignment, not handoff.
âŚbut we need to adapt
Patrick Debois is sole attendee at Andrew Shaferâs âAgile Infrastructureâ presentation,
Teams map to Applications.
a
Each team is fully repsonsible for an Application.
Teams form around applications.
Team Leaders determine whoâs in the team and what they do.
Flickr - OâReilly Velocity Conference
Ghent â Debois inadvertently popularises âDevOpsâ as a term
Flickr - OâReilly Velocity Conference
Ghent â Debois inadvertently popularises âDevOpsâ as a term
âFelonyâ to commit code and leave the office before confirming all is green.
I spoke with Gary Gruver, who led the transformation:
Teams map to Applications.
a
Each team is fully repsonsible for an Application.
Teams form around applications.
Team Leaders determine whoâs in the team and what they do.
Teams map to Applications.
a
Each team is fully repsonsible for an Application.
Teams form around applications.
Team Leaders determine whoâs in the team and what they do.
Very little mindshare for established ITSM tools.
Conference âtrade floor namesâ: VictorOps, PagerDuty, etc.
Non-IT incident frameworks getting traction
(e.g. âIncident Command Systemâ â originating in Emergency Services).
Very little mindshare for established ITSM tools.
Conference âtrade floor namesâ: VictorOps, PagerDuty, etc.
Non-IT incident frameworks getting traction
(e.g. âIncident Command Systemâ â originating in Emergency Services).
âThus if you 'write a bug' you canât fix it, unless it happens to have been prioritized and you happen to be picking up the next task in the queue.
âAlthough this approach is supposed to motivate developers to write easy to maintain systems, in fact it simply means they also do the job of the helpdesk/support/ operationsâ