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

A DevOps journey: why the sociotechnical architecture is important

João Rosa
October 08, 2019

A DevOps journey: why the sociotechnical architecture is important

In recent years, we observed some DevOps transformations across the globe. Like any transformation, there are uncertainty and pain from it, given the teams and people are asked to change their values, principles and practices.

One of the aspects of a DevOps transformation is the impacts on the culture of the organisation, mainly on the social structures. With the ambition of breaking silos, it also forces people to create new relationships, given the team composition changes. The new DevOps teams gain new capabilities, are their scope changes. The potential cascading effects are the misalignment with the business goals and miss the fundamental point of DevOps, eliminate waste.

Join João and Kenny on their journey of the recent past, where they were involved on DevOps transformations. During the transformations, they applied some heuristics from Sociotechnical Architecture and Domain-Driven Design to accelerate the business capabilities of the DevOps teams. They will share the lessons learned, from the pitfalls, failures and successes!

João Rosa

October 08, 2019

More Decks by João Rosa

Other Decks in Technology


  1. Photo by Mimi Thian on Unsplash DevOps is not a

    goal, but a never-ending process of continual improvement Jez Humble “ @joaoasrosa @kenny_baas
  2. @joaoasrosa @kenny_baas Discussing “DevOps” tools. A holy war on my

    tool vs your tool! Photo by Lachlan Donald on Unsplash
  3. @joaoasrosa @kenny_baas Photo by Ankit Patel on Unsplash Architects should

    focus on engineers and outcomes, not tools or technologies Nicole Forsgren “
  4. Photo by Timon Studler on Unsplash Investments in technology are

    also investments in people, and these investments will make our technology process more sustainable Nicole Forsgren “ @joaoasrosa @kenny_baas
  5. Photo by Patrick Tomasso on Unsplash @joaoasrosa @kenny_baas You should

    certainly take universally useful principles (...) you need to also be mindful of how your culture will react / respond. Simon Wardley “
  6. 17 Strategic Software Delivery Consultants Domain-Driven Design Continuous Delivery -

    EventStorming - Visual collaborators - Facilitators @kenny_baas baasie.com @joaoasrosa joaorosa.io
  7. Photo by Alexis Brown on Unsplash Listen to seek understanding,

    not to respond! @joaoasrosa @kenny_baas
  8. Photo by DESIGNECOLOGIST on Unsplash Create the master plan to

    rule the DevOps journey @joaoasrosa @kenny_baas
  9. @joaoasrosa @kenny_baas Photo by Jean-Frederic Fortier on Unsplash The Magical

    Number Seven, Plus or Minus Two: Some Limits on Our Capacity for Processing Information George A. Miller “
  10. 34 If we have a system of improvement that is

    directed at improving the parts taken separately. You can be absolutely sure that the improvement of the whole will not be improved. https://www.youtube.com/watch?v=OqEeIG8aPPk Russ Ackoff @joaoasrosa @kenny_baas
  11. Photo by NASA on Unsplash See the system as a

    whole Business and IT alignment @joaoasrosa @kenny_baas
  12. 38 @joaoasrosa @kenny_baas 1. Pick the culture change needed for

    your context 2. Start having meaningful conversation, listen to understand 3. Don’t force your plan, guide with measurable outcomes 4. Visualise (socio) complexity 5. See the system as a whole, design shared models between business and IT Sociotechnical systems takeaways