Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

Disciplined Agile Release Management: Going Beyond Agile Release Trains

1.733 Aufrufe

Veröffentlicht am

For medium to large-size organizations, Release Management is an important part of your DevOps and IT strategies. In this webinar Scott Ambler works through the Release Management process blade of the Disciplined Agile framework. We describe critical principles for effective release management; several potential release management strategies including agile release trains (ARTs), agile release streams, and as-needed releases; release/deployment infrastructures; and potential collaboration strategies. Every organization’s context is different, so having choices in how you approach release management is critical to developing a streamlined strategy that is right for you.

Veröffentlicht in: Software

Disciplined Agile Release Management: Going Beyond Agile Release Trains

  1. 1. Scott W. Ambler Senior Consulting Partner scott [at] scottambler.com @scottwambler Disciplined Agile Release Management Going Beyond Agile Release Trains
  2. 2. Please input your questions into the question chat field © Disciplined Agile Consortium 2
  3. 3. Agenda •  Our principles •  Our scope •  Why release management? •  Defining release management •  The release management mindset •  Release management strategies •  Parting thoughts © Disciplined Agile Consortium 3
  4. 4. © Disciplined Agile Consortium 4
  5. 5. The Seven Principles of Disciplined Agile © Disciplined Agile Consortium 5 Delight Customers Pragmatism Be Awesome Context Counts Choice is Good Optimize Flow Enterprise Awareness
  6. 6. © Disciplined Agile Consortium 6 Our Scope
  7. 7. DevOps at a Small Company © Disciplined Agile Consortium 7 •  As there is only a handful of product teams, a “you build it, you run it” approach is straightforward •  Release/deployment of a solution is handled by the delivery team responsible for that solution •  Any deployment collisions or problems are handled at the time
  8. 8. DevOps at a Large Company © Disciplined Agile Consortium 8 •  Roles tend to become more distinct as operational complexity grows •  When there are many product/delivery teams, the need to support common strategic functionality increases
  9. 9. Disciplined DevOps © Disciplined Agile Consortium 9
  10. 10. There are several reasons why you might need release management: 1.  Your organization has a complex operational infrastructure 2.  There are many delivery teams working in parallel 3.  IT delivery teams need help to release their solutions into production © Disciplined Agile Consortium 10
  11. 11. Defining Release Management Release Management addresses the coordination and streamlining of solution deployments across your organization. This includes: •  Working with delivery teams to help them to automate their deployment processes as much as possible •  To coordinate across teams to reduce the chance of collision •  To provide intelligence to the rest of the organization to improve their decision making around releases © Disciplined Agile Consortium 11
  12. 12. The Disciplined Agile Release Management Mindset 1.  Ensure successful deployments 2.  Release solutions, not just systems 3.  Enable teams to deploy 4.  Help teams streamline how they deploy 5.  Support a multi-modal environment © Disciplined Agile Consortium 12
  13. 13. Release Management Enables Delivery Teams •  Delivery teams are responsible for deploying their own solutions •  BUT: –  Not everyone is doing continuous integration (CI)/continuous deployment (CD), so this may not be fully automated yet –  Regulatory compliance may require a Separation of Concerns (SoC) when it comes to deployment (which can be automated) –  There is opportunity for reuse of tooling, guidelines, and strategies across teams © Disciplined Agile Consortium 13
  14. 14. Support a Multi-Modal Environment © Disciplined Agile Consortium 14 Frequency Predictability Low High Annual+Hourly
  15. 15. Release Management Strategies © Disciplined Agile Consortium 15
  16. 16. © Disciplined Agile Consortium 16
  17. 17. © Disciplined Agile Consortium 17
  18. 18. •  The way that you schedule the releases within a program (a large team of teams) is different than the way you schedule releases in a multi-team organization •  When to release something is determined by an array of factors, some of which are beyond the control of a single delivery team © Disciplined Agile Consortium 18 Determine Release Schedule
  19. 19. Agile Release Trains •  Appropriate for program release management (e.g. SAFe) •  The sub-teams often are required to have the same cadence, or at least a multiplier cadence (i.e. 1, 2, 4 weeks or 1, 2, 3, 6 weeks) •  Too heavy and constraining at the organizational level © Disciplined Agile Consortium 19
  20. 20. Release Stream •  Teams are allowed to release when it’s appropriate for them •  Appropriate for both program-level and organizational level release management © Disciplined Agile Consortium 20
  21. 21. As Needed Releases •  Sometimes “stuff” happens: –  You need to release a patch from a vendor –  You need to release a bug-fix –  Your stakeholders need/demand a new feature •  However, you need to be aware of: –  Release windows –  Blackout periods –  Dependencies –  Other releases happening in parallel •  This strategy enhances both release streams and release trains © Disciplined Agile Consortium 21
  22. 22. •  Delivery teams should be responsible for their own releases •  There must be a determination of whether the solution is production ready (this can be automated) •  Relevant release intelligence should be captured (what was released, when, quality levels, …) © Disciplined Agile Consortium 22 Release Solution
  23. 23. •  A primary aim of Release Management should be to enable delivery teams to be as self- sustaining as possible •  This includes: –  Coaching and mentoring them in deployment tooling and practices –  Helping them to automate wherever possible –  Helping them to plan © Disciplined Agile Consortium 23 Enable Delivery Teams
  24. 24. •  Effective governance is based on motivation and enablement, not command and control •  Release managers will work with delivery teams to develop appropriate governance and to automate the gathering and dissemination of insightful intelligence (metrics) © Disciplined Agile Consortium 24 Evolve Release Guidance
  25. 25. © Disciplined Agile Consortium 25
  26. 26. Success Requires… © Disciplined Agile Consortium 26 A Flexible Mindset Great People Collaborating and Learning Together Context-Sensitive Strategies
  27. 27. Join the DA Community! Anyone who attends a Disciplined Agile presentation or workshop is entitled to sign up at DisciplinedAgileConsortium.org to register for the designation “Disciplined Agilist” Seriously though, the DA designation is an important first step towards earning an actual DA certification, such as: More importantly, it gives you access to our “members only” information and webinars at DisciplinedAgileConsortium.org © Disciplined Agile Consortium 27
  28. 28. Do you wish your organization’s leaders had a better understanding of agile? An Executive’s Guide to Disciplined Agile can help with that! © Disciplined Agile Consortium 28
  29. 29. Thank You! Scott [at] scottambler.com @scottwambler DisciplinedAgileConsortium.org DisciplinedAgileDelivery.com ScottAmbler.com Disciplined Agile Delivery © Disciplined Agile Consortium 29
  30. 30. Scott Ambler + Associates is the thought leader behind the Disciplined Agile (DA) framework and its application. We are a management consulting firm that advises organizations to be more effective applying disciplined agile and lean processes within the context of your business. Our website is ScottAmbler.com We can help © Disciplined Agile Consortium 30
  31. 31. Additional Slides © Disciplined Agile Consortium 31
  32. 32. © Disciplined Agile Consortium 32