Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Architecture and DevOps - How to deliver sustainable quality in an ever-changing environment

Architecture and DevOps - How to deliver sustainable quality in an ever-changing environment

Most talks we hear at conferences talk about the meta perspective: making the Scrum Master even better at coaching agile teams, exploring product opportunities with new and interesting canvas solutions. But we don't feel there is enough focus on the people on the ground delivering products. This would really move the Scrum downfield in our opinion. This talk is such a talk that is usually missing... Software Architecture is about the important things, where "important" means high-risk and hard-to-change decisions. DevOps tries to develop a culture where constant experimentation and learning takes place while the environment changes rapidly. How can this go together? In this talk we will talk about general strategies agile teams can use to build and foster a DevOps culture while at the same time ensuring high-quality and sustainable software delivery. These strategies will be illustrated with real-world examples from different domains and environments. While discussing these examples we will make the general ideas and principles tangible and connect them with proven and executable practices that can directly be applied. After this talk every member of the audience will be equipped with at least one concrete idea to be tried and implemented immediately.

Peter Götz

July 07, 2022

More Decks by Peter Götz

Other Decks in Technology


  1. Architecture & DevOps Scrum Day, 2022 @DevOps_Events

  2. What is Software Architecture? Significant* design decisions *Significant: measured by

    cost of change
  3. What is DevOps? The Three Ways of DevOps 1. Flow

    / Systems Thinking 2. Amplify Feedback Loops 3. Culture of Continual Experimentation and Learning
  4. 1st Strategy: Keep It Local And Simple

  5. 2nd Strategy: Work With Focus, Flow, And Joy

  6. 3rd Strategy: Improve Your Work Every Day

  7. 4th Strategy: Create Psychological Safety

  8. 5th Strategy: Focus On Your Customer

  9. What is DevOps? The Five Ideals of DevOps 1. Locality

    and Simplicity 2. Focus, Flow, and Joy 3. Improvement of Daily Work 4. Psychological Safety 5. Customer Focus 4. Psychological Safety 1. Locality & Simplicity 2. Focus, Flow & Joy 3. Im provem ent of Daily Work 5. Customer Focus
  10. Where is a connection between DevOps and Architecture in your

  11. Why is this connection important to you and your team?

  12. Find one thing that you can do to improve your

    architecture by using DevOps strategies.
  13. About Us Peter Götz peter@devops-events.de @petersgoetz Join us for our

    next DevOps Lab training https://www.devops-events.de/ trainings/devops-lab Oliver Hankeln oliver@devops-events.de @mydalon Scan here for your 10 Star review…
  14. Literature ▪ The DevOps Handbook, Gene Kim et al. (ISBN

    978-1950508402) ▪ The Phoenix Project, Gene Kim et al. (ISBN 978-1942788294) ▪ The Unicorn Project, Gene Kim (ISBN 978-1942788768) ▪ Hands-on Domain-driven Design, Michael Plöd (https://leanpub.com/ddd-by-example) ▪ Illustrations by Muriel Hankeln (muriel@hankeln-online.de)