Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Everyone is Part of Continuous Delivery @ All Day DevOps (Oct 2017)

210 views

Published on

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.

Published in: Technology

Everyone is Part of Continuous Delivery @ All Day DevOps (Oct 2017)

  1. 1. Everyone is Part of Continuous Delivery Manuel Pais Delivery Coach and Technologist manuelpais.net @manupaisable
  2. 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. 3. About me Manuel Pais MS Software Eng @manupaisable manuelpais.net manuel.pais@gmail.com Delivery Coach and Technologist Focused on teams and flow
  4. 4. Takeaways 1. Beyond built-test-deploy pipelines 2. Stereotypes tear us apart 3. Build trust step-by-step 4. How inclusive pipeline looks like
  5. 5. what’s missing?
  6. 6. what’s missing? we tend to care about technical bits only…
  7. 7. “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
  8. 8. Example #1 Make activities visible to find bottlenecks
  9. 9. Integration Tests Functional Tests Performance Tests Operational Acceptance PROD Initial state: serial pipeline
  10. 10. Integration Tests Functional Tests Performance Tests Operational Acceptance PROD Initial state: client goals
  11. 11. Infra Team Dev Team
  12. 12. Infra Team Dev Team
  13. 13. Infra Team Dev Team
  14. 14. painful bottlenecks in team interactions
  15. 15. bottlenecks = silos time is lost in queues, not execution
  16. 16. Future state: automated provisioning
  17. 17. Future state: automated provisioning
  18. 18. Future state: automated provisioning
  19. 19. Future state: automated provisioning
  20. 20. Future state: Dev and Infra Teams??? Dev Team Infra Team
  21. 21. Infra Team Dev Team
  22. 22. Infrastructure Verification Tests (IVTs)
  23. 23. Infra Team Dev Team
  24. 24. fast feedback? short lead time?
  25. 25. faster and faster feedback! shorter and shorter lead times!
  26. 26. Takeaways 1. Beyond built-test-deploy pipelines 2. Stereotypes tear us apart 3. Build trust step-by-step 4. How inclusive pipeline looks like
  27. 27. stereotypes
  28. 28. Build Test Deploy DEV QA OPS Security
  29. 29. Build Test Deploy DEV QA OPS Security Marketing
  30. 30. Build Test Deploy DEV QA OPS Network Security Marketing
  31. 31. Build Test Deploy DEV QA OPS Security Network Marketing Infra
  32. 32. Build Test Deploy DEV QA OPS Security Marketing Legal Network Infra
  33. 33. Build Test Deploy DEV QA OPS Security Marketing Legal Network Infra GDPR
  34. 34. Build Test Deploy DEV QA OPS Security Marketing Legal Network Infra GDPR fines up to 4% global revenue
  35. 35. BizDevOps
  36. 36. BizInfraDevOps
  37. 37. BizInfraLegalDevOps
  38. 38. BizInfraLegalNetDataDevOps
  39. 39. BizInfraLegalNetDataDevSecOps
  40. 40. be weary of buzzwords everyone needed on board
  41. 41. stereotypes
  42. 42. Takeaways 1. Beyond built-test-deploy pipelines 2. Stereotypes tear us apart 3. Build trust step-by-step 4. How inclusive pipeline looks like
  43. 43. automation is not the goal, but the means to an end… Faster and Safer Delivery
  44. 44. automation is not the goal, but the means to an end… Faster and Safer Delivery
  45. 45. automating hand-offs requires trust… which in turn requires time
  46. 46. “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
  47. 47. breaking down silos is hard… build TRUST first!
  48. 48. Client example #2 Evolve pipeline to establish trust points
  49. 49. https://github.com/manupaisable/pipeline-as-code Initial state: serial pipeline
  50. 50. https://github.com/manupaisable/pipeline-as-code Intermediate state: CAB in path to prod
  51. 51. End state: short and wide pipeline https://github.com/manupaisable/pipeline-as-code
  52. 52. build trust step-by-step think of right tools for current trust level? sense what each team is comfortable with
  53. 53. Takeaways 1. Beyond built-test-deploy pipelines 2. Stereotypes tear us apart 3. Build trust step-by-step 4. How inclusive pipeline looks like
  54. 54. Amy, the Product Owner
  55. 55. Amy, the Product Owner
  56. 56. Mark, the Compliance Officer
  57. 57. non-technical stakeholders are part of delivery too
  58. 58. pipeline = (real) workflow highlight bottlenecks => build bridges trust requires time => automate gradually not just technical => include everyone
  59. 59. pipeline = (real) workflow highlight bottlenecks => build bridges trust requires time => automate gradually not just technical => include everyone
  60. 60. pipeline = (real) workflow highlight bottlenecks => build bridges trust requires time => automate gradually not just technical => include everyone
  61. 61. 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
  62. 62. (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
  63. 63. 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
  64. 64. releasabilitybook.com Upcoming book: Team Guide to Software Releasability by Chris O’Dell & Manuel Pais
  65. 65. Session Title Your Name Your Title Your Company Your @TwitterHandle
  66. 66. Session Title Your Name Your Title Your Company Your @TwitterHandle
  67. 67. October 24, 2017 Thank You All Day DevOps Organizers!
  68. 68. 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

×