Getting full value from Continuous Delivery means catering for the needs of everyone in the organization: business, devs, ops, etc. Pipelines are excellent for visualizing work status. But even better when they increase collaboration by highlighting bottlenecks due to hand-offs between siloed teams.

1. Everyone is Part of Continuous Delivery
Manuel Pais
Delivery Coach and Technologist
manuelpais.net
@manupaisable

2. Takeaways
1. Beyond built-test-deploy pipelines
2. Stereotypes tear us apart
3. Build trust step-by-step
4. How inclusive pipeline looks like

3. About me
Manuel Pais
MS Software Eng
@manupaisable
manuelpais.net
manuel.pais@gmail.com
Delivery Coach and Technologist
Focused on teams and flow

5. Takeaways
1. Beyond built-test-deploy pipelines
2. Stereotypes tear us apart
3. Build trust step-by-step
4. How inclusive pipeline looks like

6. what’s missing?

7. what’s missing?
we tend to care about
technical bits only…

8. “The idea behind the deployment
pipeline is to model the part of your
project's value stream that goes
from check-in to release, and then
to automate it.”
–Jez Humble
https://continuousdelivery.com/2010/02/continuous-delivery

9. Example #1
Make activities visible
to find bottlenecks

10. Integration
Tests
Functional
Tests
Performance
Tests
Operational
Acceptance
PROD
Initial state: serial pipeline

11. Integration
Tests
Functional
Tests
Performance
Tests
Operational
Acceptance
PROD
Initial state: client goals

15. Infra Team
Dev Team

16. Infra Team
Dev Team

17. Infra Team
Dev Team

18. painful bottlenecks
in team interactions

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

20. Future state: automated provisioning

21. Future state: automated provisioning

22. Future state: automated provisioning

23. Future state: automated provisioning

24. Future state: Dev and Infra Teams???
Dev Team Infra Team

25. Infra Team
Dev Team

26. Infrastructure Verification Tests (IVTs)

27. Infra Team
Dev Team

28. fast feedback?
short lead time?

30. faster and faster feedback!
shorter and shorter lead
times!

31. Takeaways
1. Beyond built-test-deploy pipelines
2. Stereotypes tear us apart
3. Build trust step-by-step
4. How inclusive pipeline looks like

32. stereotypes

33. Build Test Deploy
DEV QA OPS
Security

34. Build Test Deploy
DEV QA OPS
Security
Marketing

35. Build Test Deploy
DEV QA OPS
Network
Security
Marketing

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

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

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

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

42. BizDevOps

43. BizInfraDevOps

44. BizInfraLegalDevOps

45. BizInfraLegalNetDataDevOps

46. BizInfraLegalNetDataDevSecOps

47. be weary of buzzwords
everyone needed on board

48. stereotypes

49. Takeaways
1. Beyond built-test-deploy pipelines
2. Stereotypes tear us apart
3. Build trust step-by-step
4. How inclusive pipeline looks like

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

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

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

55. “First of all, you have to accept that you are always
going to draw meaning and inferences from what
others say and do, based on your past experience.
It’s how people work.”
Ladder of Inference
https://www.skillsyouneed.com/ips/ladder-of-inference.html

56. breaking down silos is
hard…
build TRUST first!

58. Client example #2
Evolve pipeline
to establish trust points

59. https://github.com/manupaisable/pipeline-as-code
Initial state: serial pipeline

60. https://github.com/manupaisable/pipeline-as-code
Intermediate state: CAB in path to prod

61. End state: short and wide pipeline
https://github.com/manupaisable/pipeline-as-code

62. build trust step-by-step
think of right tools for
current trust level?
sense what each team
is comfortable with

63. Takeaways
1. Beyond built-test-deploy pipelines
2. Stereotypes tear us apart
3. Build trust step-by-step
4. How inclusive pipeline looks like

65. Amy, the Product Owner

66. Amy, the Product Owner

67. Mark, the Compliance Officer

68. non-technical stakeholders
are part of delivery too

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

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

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

72. 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

73. (Future) Reference
Dominica DeGrandis, 2017, ‘Making Work Visible’
https://itrevolution.com/book/making-work-visible
Talk at DevOps Enterprise Summit Europe 2017
https://www.youtube.com/watch?v=KR7Y8IUgyyA

74. Other references
• 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
• Cycle of Mistrust
https://www.industriallogic.com/blog/cycles-of-mistrust
• 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

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

76. Session Title
Your Name
Your Title
Your Company
Your @TwitterHandle

77. Session Title
Your Name
Your Title
Your Company
Your @TwitterHandle

78. October 24, 2017
Thank You All Day DevOps Organizers!

79. bit.ly/addo-slack
Find me on slack, right now!
Manuel Pais
Delivery Coach and Technologist
thank you and please give feedback:
buff.ly/2zz0iEf
#continuous-everything
@manupaisable
manuelpais.net