The document discusses continuous delivery and DevOps. It argues that continuous delivery and DevOps are not just about tools but also culture. It emphasizes including everyone beyond just development teams in the delivery process to make it sustainable, visible, flexible, empowered and accountable. Automation helps with delivery but is a means to an end, not the goal, and building trust requires automating gradually.

1. Everyone is Part of
Continuous Delivery
Manuel Pais | Skelton Thatcher Consulting
@manupaisable | skeltonthatcher.com

2. Today
1. Continuous Delivery or DevOps?
2. Make Work Bottlenecks Visible
3. Automate… Eventually
4. Include Everyone

3. About me
Manuel Pais
@manupaisable
Consultant at
Skelton Thatcher Consulting

4. Team-first digital transformation
30+ organisations
UK, US, DE, PT, India, China
skeltonthatcher.com

6. Today
1. Continuous Delivery or DevOps?
2. Make Work Bottlenecks Visible
3. Automate… Eventually
4. Include Everyone

7. “DevOps brought to the attention
that two worlds, typically apart in a
company, need to collaborate and
that actually gives you a
competitive edge”
–Patrick Debois
infoq.com/interviews/debois-devops

8. “ability to get changes of all types,
into production, or into the hands
of users, safely and quickly in a
sustainable way”
–Jez Humble
continuousdelivery.com

10. cdchecklist.info

11. Continuous
Delivery
DevOps
– my mind in 2010…

12. Continuous
Delivery
DevOps
TOOLS CULTURE
– my mind in 2010…

13. Continuous
Delivery
DevOps
TOOLS CULTURE
– my mind in 2017…

14. Continuous
Delivery
DevOps
TOOLS
– (still) some people in 2017…

15. Today
1. Continuous Delivery or DevOps?
2. Make Work Bottlenecks Visible
3. Automate… Eventually
4. Include Everyone

16. “Agile System Administration was
too long and too narrow… ”
–Patrick Debois
infoq.com/interviews/debois-devops

17. what’s missing?
Build Test Deploy

18. what’s missing?
we tend to care about
technical bits only…
Build Test Deploy

19. Integration
Tests
Functional
Tests
Performance
Tests
Operational
Acceptance
PROD

33. painful bottlenecks
in team interactions

34. bottlenecks = silos
time is lost in queues,
not execution

35. Today
1. Continuous Delivery or DevOps?
2. Make Work Bottlenecks Visible
3. Automate… Eventually
4. Include Everyone

36. automation is not the goal,
but the means to an end…
Faster and Safer Delivery

37. automation is not the goal,
but the means to an end…
Faster and Safer Delivery

38. Infra Team
Dev Team

39. Infra Team
Dev Team

40. Infra Team
Dev Team

41. Infra Team
Dev Team

42. Infra Team
Dev Team

43. Infra Team
Dev Team

44. Infra Team
Dev Team

45. automating hand-offs
requires trust… which in
turn requires time

46. breaking down silos is
HARD!

47. Today
1. Continuous Delivery or DevOps?
2. Make Work Bottlenecks Visible
3. Automate… Eventually
4. Include Everyone

48. “ability to get changes of all types,
into production, or into the hands
of users, safely and quickly in a
sustainable way”
–Jez Humble
continuousdelivery.com

49. Role
Activity
automated
manual

50. Build Test Deploy
DEV QA OPS

51. Build Test Deploy
DEV QA OPS
Security

52. Build Test Deploy
DEV QA OPS
Security
Marketing

53. Build Test Deploy
DEV QA OPS
Network
Security
Marketing

54. Build Test Deploy
DEV QA OPS
Security
Network
Marketing
Infra

55. Build Test Deploy
DEV QA OPS
Security
Marketing
Legal
Network
Infra

56. Build Test Deploy
DEV QA OPS
Security
Marketing
Legal
Network
Infra
GDPR

57. Build Test Deploy
DEV QA OPS
Security
Marketing
Legal
Network
Infra
GDPR
fines up to
4% global
revenue

58. Build Test Deploy
DEV QA OPS
Security
Marketing
Legal
Network
Infra

59. Build Test Deploy
DEV QA OPS
Security
Marketing
Legal
Network
Infra

60. Build Test Deploy
DEV QA OPS
Security

61. Build
Func
Tests
Deploy
DEV QA OPS
Sec
Tests
SECURITY

62. Build
Func
Tests
Deploy
DEV QA OPSSECURITY
Sec
Tests
Pen
Tests
SECURITY

63. Short and Wide Pipeline

64. Build
Func
Tests
Deploy
DEV QA OPSSECURITY
Sec
Tests
Pen
Tests
SECURITY

65. Build
Func
Tests
Deploy
DEV QA OPSSECURITY
Sec
Tests
Pen
Tests
SECURITY

66. Change
Request
MARKETING
Build
Func
Tests
Deploy
DEV QA OPSSECURITY
Sec
Tests
Pen
Tests
SECURITY

67. Change
Request
MARKETING
Approve
Deploy
MARKETING
Build
Func
Tests
Deploy
DEV QA OPSSECURITY
Sec
Tests
Pen
Tests
SECURITY

68. Change
Request
MARKETING
Approve
Deploy
MARKETING
Build
Func
Tests
Deploy
DEV QA OPSSECURITY
Sec
Tests
Pen
Tests
SECURITY
Provision
NETWORK
INFRA

69. Change
Request
MARKETING
Approve
Deploy
MARKETING
Build
Func
Tests
Deploy
DEV QA OPSSECURITY
Sec
Tests
Pen
Tests
SECURITY
Provision
NETWORK
INFRA
Approve
Change
LEGAL

71. non-technical stakeholders
are part of delivery too

72. “ability to get changes of all types,
into production, or into the hands
of users, safely and quickly in a
sustainable way”
–Jez Humble
continuousdelivery.com

73. sustainable
visible
flexible
empowered
accountable

74. sustainable
visible
flexible
empowered
accountable

75. sustainable
visible
flexible
empowered
accountable

76. Change
Request
MARKETING
Approve
Deploy
MARKETING
DeployBuild
Func
Tests
DEV QA OPSSECURITY
Sec
Tests
Pen
Tests
SECURITY
Provision
NETWORK
INFRA
Approve
Change
LEGAL

77. Change
Request
MARKETING
Approve
Deploy
MARKETING
Build
Func
Tests
Deploy
DEV QA OPSSECURITY
Sec
Tests
Pen
Tests
SECURITY
Provision
NETWORK
INFRA
Approve
Change
LEGAL

78. Change
Request
MARKETING
Approve
Deploy
MARKETING
Build
Func
Tests
Deploy
DEV OPSSECURITY
Sec
Tests
QA
Pen
Tests
SECURITY
Provision
NETWORK
INFRA
Approve
Change
LEGAL

79. Change
Request
MARKETING
Approve
Deploy
MARKETING
Build
Func
Tests
Deploy
DEV OPSSECURITY
Sec
Tests
QA
Pen
Tests
SECURITY
Provision
NETWORK
INFRA
Approve
Change
LEGAL

80. Change
Request
MARKETING
Approve
Deploy
MARKETING
Build
Func
Tests
Deploy
DEV OPSSECURITY
Sec
Tests
QA
Pen
Tests
SECURITY
Provision
NETWORK
INFRA
Approve
Change
LEGAL

81. sustainable
visible
flexible
empowered
accountable

82. “ability to get changes of all types,
into production, or into the hands
of users, safely and quickly in a
visible, flexible, empowered,
and accountable way”

83. Today
1. Continuous Delivery or DevOps?
2. Make Work Bottlenecks Visible
3. Automate… Eventually
4. Include Everyone

84. pipeline = (real) workflow
highlight bottlenecks => build bridges
trust requires time => automate gradually
not just technical => include everyone

85. pipeline = (real) workflow
highlight bottlenecks => build bridges
trust requires time => automate gradually
not just technical => include everyone

86. pipeline = (real) workflow
highlight bottlenecks => build bridges
trust requires time => automate gradually
not just technical => include everyone

87. 2010 DevOpsDays intro
https://www.youtube.com/watch?v=EOveXZhJpr4

88. References
Gene Kim, Kevin Behr, 2013, ‘The Phoenix Project’
• Don G. Reinertsen, 2009, ‘The Principles of
Product Development Flow: Second
Generation Lean Product Development’
1h30 summary
https://www.youtube.com/watch?v=L6v6W7jkwok

89. References
• Continuous Delivery Checklist Template
http://cdchecklist.info
• Continuous Delivery Anti-Patterns
https://dzone.com/articles/continuous-delivery-anti-patterns
• The Three Ways: The Principles Underpinning DevOps
https://itrevolution.com/the-three-ways-principles-underpinning-devops
• Ladder of Inference
https://www.skillsyouneed.com/ips/ladder-of-inference.html
• Q&A with Immuta on the Implications of EU’s General Data Protection
Regulation (GDPR)
https://www.infoq.com/articles/immuta-gdpr-implications
• Securing a Continuous Delivery Pipeline
https://dzone.com/articles/securing-a-continuous-delivery-pipeline

90. releasabilitybook.com
Upcoming book:
Team Guide to
Software Releasability
by Chris O’Dell & Manuel Pais

91. thank you
Manuel Pais
@manupaisable
manuel.pais@skeltonthatcher.com
skeltonthatcher.com

92. Merging Agile/CD/DevOps
• include ops, support or infra specialists in your dev team
• plan operability and security stories and add to the
backlog, with an appropriate format (e.g. “what/why”)
• track “planned” and “unplanned” velocity… or use Kanban
• “done” means “live”... or even “retired”
• Scrum Master *must* understand DevOps goals
• Product Owners understand and prioritize operability
• consider devs/PO/SM on call