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
Tweet

More Decks by João Rosa

Other Decks in Technology

Transcript

  1. A DevOps journey:
    why the sociotechnical
    architecture is important

    View Slide

  2. Photo by Mimi Thian on Unsplash
    DevOps is not a goal, but a never-ending
    process of continual improvement
    Jez Humble

    @joaoasrosa @kenny_baas

    View Slide

  3. 3
    @joaoasrosa @kenny_baas

    View Slide

  4. @joaoasrosa @kenny_baas

    View Slide

  5. Cargo Cult
    @joaoasrosa @kenny_baas

    View Slide

  6. @joaoasrosa @kenny_baas
    Discussing “DevOps” tools.
    A holy war on my tool vs your tool!
    Photo by Lachlan Donald on Unsplash

    View Slide

  7. @joaoasrosa @kenny_baas
    Photo by Ankit Patel on Unsplash
    Architects should focus on engineers and
    outcomes, not tools or technologies
    Nicole Forsgren

    View Slide

  8. 8
    @joaoasrosa @kenny_baas
    Copyright Alistair Cockburn - https://twitter.com/totheralistair/status/978413240182034432
    Individuals and Interactions Over Processes and Tools

    View Slide

  9. 9
    @joaoasrosa @kenny_baas
    Agile ≠
    https://wiki.almworks.com/display/structure/Structure+on+Agile+Boards
    Jira Over Individuals and Interactions

    View Slide

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

    View Slide

  11. Sociotechnical systems
    Photo by frank mckenna on Unsplash
    @joaoasrosa @kenny_baas

    View Slide

  12. Shifting the burden to the intervenor
    Photo by Wil Stewart on Unsplash
    @joaoasrosa @kenny_baas

    View Slide

  13. @joaoasrosa @kenny_baas

    View Slide

  14. @joaoasrosa @kenny_baas

    View Slide

  15. @joaoasrosa @kenny_baas

    View Slide

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

    View Slide

  17. 17
    Strategic Software Delivery
    Consultants
    Domain-Driven Design
    Continuous Delivery - EventStorming
    - Visual collaborators - Facilitators
    @kenny_baas
    baasie.com
    @joaoasrosa
    joaorosa.io

    View Slide

  18. @joaoasrosa @kenny_baas
    Photo by REVOLT on Unsplash

    View Slide

  19. 19
    @joaoasrosa @kenny_baas
    https://www.managementboek.nl/boek/9781138361584/the-corporate-tribe-engels-danielle-braun

    View Slide

  20. Photo by Benjamin Child on Unsplash
    @joaoasrosa @kenny_baas

    View Slide

  21. @joaoasrosa @kenny_baas
    Photo by Kevin Erdvig on Unsplash
    Meetings as campfires

    View Slide

  22. Photo by Alexis Brown on Unsplash
    Listen to seek understanding,
    not to respond!
    @joaoasrosa @kenny_baas

    View Slide

  23. 23
    @joaoasrosa @kenny_baas
    http://www.liberatingstructures.com/ls-menu

    View Slide

  24. Photo by DESIGNECOLOGIST on Unsplash
    Create the master plan to rule the
    DevOps journey
    @joaoasrosa @kenny_baas

    View Slide

  25. Provide guidance and support
    Create measurable outcomes
    @joaoasrosa @kenny_baas

    View Slide

  26. @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

    View Slide

  27. 27
    @joaoasrosa @kenny_baas

    View Slide

  28. 28
    @joaoasrosa @kenny_baas

    View Slide

  29. 29
    @joaoasrosa @kenny_baas
    Wardley Maps
    @swardley

    View Slide

  30. 30
    @joaoasrosa @kenny_baas
    Impact Mapping
    @gojkoadzic

    View Slide

  31. EventStorming
    @ziobrando
    @joaoasrosa @kenny_baas

    View Slide

  32. 32
    @joaoasrosa @kenny_baas
    Wall of Tech Debt
    @mathiasverraes

    View Slide

  33. @joaoasrosa @kenny_baas
    Photo by Micaela Parente on Unsplash

    View Slide

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

    View Slide

  35. Photo by NASA on Unsplash
    See the system as a whole
    Business and IT alignment
    @joaoasrosa @kenny_baas

    View Slide

  36. Domain-Driven Design
    Co-creating software models
    between business and IT
    @joaoasrosa @kenny_baas

    View Slide

  37. 37
    @joaoasrosa @kenny_baas

    View Slide

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

    View Slide

  39. Look for Sociotechnical Architects
    @joaoasrosa @kenny_baas

    View Slide

  40. #CatTax
    @joaoasrosa @kenny_baas

    View Slide