A fast-moving, outside-in talk that 'sells' the value of DevOps to business executives, finds the weakest link in the value stream and explores the often troubled relationship between IT people and normal people (the business). There is much hype around DevOps, so what are we actually talking about? DevOps improved Agile by speeding up deployment (and more). But how do you 'sell' DevOps to business executives who don't understand IT? No business value is realized until the users actually use the systems well. This is often the weakest link in the IT value chain, so you need to extend your scope. Collaboration is difficult and collaboration between business and IT even more so. What kind of behaviour is effective? Learn from workshop results from practitioners in 11 countries. But why "Kill DevOps"? This refers to an ancient Zen saying about a monk’s journey towards enlightenment and awakening. If you think that you’ve found Buddha, think again, because you never will. It’s the same with DevOps: it’s about continuous experimentation and learning.

1. 1
@marksmalley
Kill DevOps
DevOpsDays, Riga, 19 September 2017
Mark Smalley, The IT Paradigmologist
Current interests: Digital enterprise, IT operating models,
value of IT, business-IT relationships, co-creation of value,
multidisciplinary collaboration, working with complexity
mark.smalley@aslbislfoundation.org
itchronicles.com/author/marksmalley
www.linkedin.com/in/marksmalley
@marksmalley
www.smalley.it
I have to think about things in depth
before I can speak about them with uncertainty

2. 2
@marksmalley

3. 3
@marksmalley

4. 4
@marksmalley

5. 5
@marksmalley

6. 6
@marksmalley
Imposter syndrome

7. 7
@marksmalley
Enterprise
governance
of IT
Enterprise
architecture
Business
relationship
management
IT service
management
Business
analysis
Project
management
Agile /
DevOps
Business
information
management
Application
management
Power of perspective

8. 8
@marksmalley
1980’s: Project Mgt
 Dictatorship
1990’s: ITSM
 Bureaucracy
2000’s: Agile
 Fundamentalism
2010’s: DevOps
 …
Forty year perspective

9. 9
@marksmalley
DevOps is useless
unless seen in a bigger picture
in co-creational collaboration
with the business
Summary of Kill DevOps

10. 10
@marksmalley
Explore DevOps
‘Sell’ DevOps to business executives
Discover your weakest link
Adopt the right attitude
Agenda

11. 11
@marksmalley
Explore DevOps
‘Sell’ DevOps to business executives
Discover your weakest link
Adopt the right attitude
Agenda

12. 12
@marksmalley
Six blind men and the elephant
Snake
Spear Fan Tree
Wall
Rope

13. 13
@marksmalley
DevOps
DevOps DevOps DevOps
DevOps
DevOps
Six blind men and IT

14. 14
@marksmalley
ROI
ROI ROI ROI
ROI
ROI
Six business men and IT

15. 15
@marksmalley
Business
people
Business
goals
DevOps and ROI
IT
people
IT industry
guidance
IT systems
& services
Investment
Return on investment

16. 16
@marksmalley
Business
goals
DevOps and ROI
IT industry
guidance
IT systems
& services
Dev
Ops
Business
people
Req
Use
Investment
Return on investment

17. 17
@marksmalley
DevOps in a value stream
Req
Dev
Ops
Use
Inv Val
Inf
Bus
Info
App
Infra
Bus
Info
App
Infra

18. 18
@marksmalley
DevOps in a value stream
Req
Dev
Ops
Use
Inv Val
Inf
Bus
Info
App
Infra
Bus
Info
App
Infra
DevOps

19. 19
@marksmalley
• Prescriptive companion to The Phoenix Project
• Principles and technical practices
• Fast flow of work from
development to deployment
• World-class reliability, availability
and security
DevOps Handbook

20. 20
@marksmalley
• Development (40)
• Operations (21)
• Infrastructure (22)
67 Technical practices
for “continuous …”
Infra
Ops
Dev

21. 21
@marksmalley
1. Visualization of work, WIP,
batch sizes, handoffs,
constraints, hardship, waste
2. Problems, knowledge, quality,
downstream optimization
3. Institutionalization of
improvement, proliferation,
resilience, safe learning culture
15 Principles
for the Three Ways of DevOps
Infra
Ops
Dev
Bus

22. 22
@marksmalley
Business
goals
DevOps technical practices for continuous
integration, delivery and deployment
DevOps
technical
practices
IT systems
& services
Dev
Ops
Req
Use
Investment
Return on investment

23. 23
@marksmalley
Business
goals
DevOps principles can be applied broadly
DevOps
principles
IT systems
& services
Dev
Ops
Req
Use
Investment
Return on investment

24. 24
@marksmalley
Beware of the hype
Broad and narrow DevOps
Principles and Technical practices
DevOps Handbook
Summary
Explore DevOps

25. 25
@marksmalley
Explore DevOps
‘Sell’ DevOps to business executives
Discover your weakest link
Adopt the right attitude
Agenda

26. 26
@marksmalley
A typical IT-business conversation
DevOps is…
CIO CEO

27. 27
@marksmalley
Why should we
invest in this “DevOps”
instead of in other things?
A typical IT-business conversation
CIO CEO

28. 28
@marksmalley
Continuous containers
Immutable microservices
CALMS as code
A typical IT-business conversation
CIO CEO

29. 29
@marksmalley
That’s techno-babble!
Come back when
you speak MBA…
A typical IT-business conversation
CIO CEO

30. 30
@marksmalley
Benefits of DevOps
Faster delivery
More dependable
Cheaper

31. 31
@marksmalley
Business
goals
DevOps
guidance
Utility
Warranty
Delivery
Costs
Dev
Ops
Req
Use
IT systems and services
Fitness for purpose:
functionality
Fitness for use:
availability, reliability, security
Speed and priority of
delivery of functionality
Cost of development
and operations

32. 32
@marksmalley
Business
goals
Utility
Warranty
Delivery
Costs
Dev
Ops
Req
Use
Investment
Return on investment
Business benefits of narrow application
of DevOps’ technical practices
DevOps
technical
practices

33. 33
@marksmalley
Lower
OPEX &
CAPEX
Utility
Warranty
Delivery
Costs
Dev
Ops
Req
Use
Investment
Return on investment
Business benefits of lower IT costs
DevOps
technical
practices

34. 34
@marksmalley
Quicker
time to
market
Utility
Warranty
Delivery
Costs
Dev
Ops
Req
Use
Investment
Return on investment
Business benefits of quicker delivery
DevOps
technical
practices

35. 35
@marksmalley
Quicker
business
change
Utility
Warranty
Delivery
Costs
Dev
Ops
Req
Use
Investment
Return on investment
Business benefits of quicker delivery
DevOps
technical
practices

36. 36
@marksmalley
Fewer
business
disruptions
Utility
Warranty
Delivery
Costs
Dev
Ops
Req
Use
Investment
Return on investment
Business benefits of better warranty
(fitness for use)
DevOps
technical
practices

37. 37
@marksmalley
Lower
OPEX
DevOps
technical
practices
Utility
Warranty
Delivery
Costs
Dev
Ops
Req
Use
Investment
Return on investment
Business benefits of better warranty
(fitness for use)

38. 38
@marksmalley
Better
customer
experience
Utility
Warranty
Delivery
Costs
Dev
Ops
Req
Use
Investment
Return on investment
Business benefits of better warranty
(fitness for use)
DevOps
technical
practices

39. 39
@marksmalley
Business
goals
DevOps
principles
Utility
Warranty
Delivery
Costs
Dev
Ops
Req
Use
Investment
Return on investment
Business benefits of broad application
of DevOps’ principles

40. 40
@marksmalley
Sales
Prices
Costs
Risks
Utility
Warranty
Delivery
Costs
Dev
Ops
Req
Use
Investment
Return on investment
Business benefits of better utility
(fitness for purpose – functionality)
DevOps
principles

41. 41
@marksmalley
You again?
A better IT-business conversation
CIO CEO

42. 42
@marksmalley
So why should we
invest in this “DevOps”
instead of in other things?
A better IT-business conversation
CIO CEO

43. 43
@marksmalley
Quicker time to market
Better customer experience
Fewer costly disruptions
A better IT-business conversation
CIO CEO

44. 44
@marksmalley
Now you’re speaking
my MBA-language!
A better IT-business conversation
CIO CEO

45. 45
@marksmalley
Speed of delivery, and fitness for use and purpose
Don’t mention “IT” to business executives
Benefits, costs and risks
Summary
‘Sell’ DevOps to business executives

46. 46
@marksmalley
Explore DevOps
‘Sell’ DevOps to business executives
Discover your weakest link
Adopt the right attitude
Agenda

47. 47
@marksmalley
Where’s your weakest link?
Req
Dev
Ops
Use
Inv Val
Inf
Bus
Info
App
Infra
Bus
Info
App
Infra
What should be your
highest priority?

48. 48
@marksmalley
Work on the weakest link
• The business is often the weakest link
• They also need guidance
• Assess your situation using
the checklist in the free
‘BiSL® Next Summary’ on
www.aslbisfoundation.org

49. 49
@marksmalley
Assess your organization’s
key business responsibilities for I&T
• Ownership of information and systems
• Information needed by each business entity
• Functionality and intended use of each information system
• Value realization – actual use
• Relationship with IT
www.itchronicles.com/itsm/business-it-relationships
(findings from 15 workshops on effective business-IT behaviour)

50. 50
@marksmalley
Discover and work on your weakest link
If it’s in IT, go DevOps
If it’s in the business, go DevOps and BiSL®
Summary
Discover your weakest link

51. 51
@marksmalley
Explore DevOps
‘Sell’ DevOps to business executives
Discover your weakest link
Adopt the right attitude
Agenda

52. 52
@marksmalley

53. 53
@marksmalley
Ancient Buddhist Proverb
If you meet buddha on the road,
kill him – keep meditating!

54. 54
@marksmalley
If you meet DevOps on the road, kill it.
Keep learning and experimenting!
Ancient DevOps Proverb

55. 55
@marksmalley
Kill DevOps
DevOpsDays, Riga, 19 September 2017
Mark Smalley, The IT Paradigmologist
Current interests: Digital enterprise, IT operating models,
value of IT, business-IT relationships, co-creation of value,
multidisciplinary collaboration, working with complexity
mark.smalley@aslbislfoundation.org
itchronicles.com/author/marksmalley
www.linkedin.com/in/marksmalley
@marksmalley
www.smalley.it
I have to think about things in depth
before I can speak about them with uncertainty

56. 56
@marksmalley
• Give first-hand understanding
of what actually happens in
business operations
• Share overarching strategy
• Share stakeholders and their
interests and goals
• Share business case so that IT
understands desired outcomes
Desired business behaviour
Findings from the ‘Business-IT Relationships’
Open Space Session at DevOpsDays Riga Sept 2017
More: www.itchronicles.com/itsm/business-it-relationships
• Specify requirements clearly
• Set priorities between
‘competing’ work items
• Provide enough budget
• Contribute actively during
development, e.g. testing
• Provide fast, frequent and good
feedback