A DevOps journey: why the sociotechnical architecture is important

by João Rosa

Slide 1

Slide 1 text

Slide 2

Slide 2 text

Photo by Mimi Thian on Unsplash DevOps is not a goal, but a never-ending process of continual improvement Jez Humble “ @joaoasrosa @kenny_baas

Slide 3

Slide 3 text

3 @joaoasrosa @kenny_baas

Slide 4

Slide 4 text

@joaoasrosa @kenny_baas

Slide 5

Slide 5 text

Cargo Cult @joaoasrosa @kenny_baas

Slide 6

Slide 6 text

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

Slide 7

Slide 7 text

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

Slide 8

Slide 8 text

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

Slide 9

Slide 9 text

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

Slide 10

Slide 10 text

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

Slide 11

Slide 11 text

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

Slide 12

Slide 12 text

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

Slide 13

Slide 13 text

@joaoasrosa @kenny_baas

Slide 14

Slide 14 text

@joaoasrosa @kenny_baas

Slide 15

Slide 15 text

@joaoasrosa @kenny_baas

Slide 16

Slide 16 text

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 “

Slide 17

Slide 17 text

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

Slide 18

Slide 18 text

@joaoasrosa @kenny_baas Photo by REVOLT on Unsplash

Slide 19

Slide 19 text

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

Slide 20

Slide 20 text

Photo by Benjamin Child on Unsplash @joaoasrosa @kenny_baas

Slide 21

Slide 21 text

@joaoasrosa @kenny_baas Photo by Kevin Erdvig on Unsplash Meetings as campﬁres

Slide 22

Slide 22 text

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

Slide 23

Slide 23 text

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

Slide 24

Slide 24 text

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

Slide 25

Slide 25 text

Provide guidance and support Create measurable outcomes @joaoasrosa @kenny_baas

Slide 26

Slide 26 text

@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 “

Slide 27

Slide 27 text

27 @joaoasrosa @kenny_baas

Slide 28

Slide 28 text

28 @joaoasrosa @kenny_baas

Slide 29

Slide 29 text

29 @joaoasrosa @kenny_baas Wardley Maps @swardley

Slide 30

Slide 30 text

30 @joaoasrosa @kenny_baas Impact Mapping @gojkoadzic

Slide 31

Slide 31 text

EventStorming @ziobrando @joaoasrosa @kenny_baas

Slide 32

Slide 32 text

32 @joaoasrosa @kenny_baas Wall of Tech Debt @mathiasverraes

Slide 33

Slide 33 text

@joaoasrosa @kenny_baas Photo by Micaela Parente on Unsplash

Slide 34

Slide 34 text

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 Ackoﬀ @joaoasrosa @kenny_baas

Slide 35

Slide 35 text

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

Slide 36

Slide 36 text

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

Slide 37

Slide 37 text

37 @joaoasrosa @kenny_baas

Slide 38

Slide 38 text

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

Slide 1

Slide 1 text

Slide 2

Slide 2 text

Slide 3

Slide 3 text

Slide 4

Slide 4 text

Slide 5

Slide 5 text

Slide 6

Slide 6 text

Slide 7

Slide 7 text

Slide 8

Slide 8 text

Slide 9

Slide 9 text

Slide 10

Slide 10 text

Slide 11

Slide 11 text

Slide 12

Slide 12 text

Slide 13

Slide 13 text

Slide 14

Slide 14 text

Slide 15

Slide 15 text

Slide 16

Slide 16 text

Slide 17

Slide 17 text

Slide 18

Slide 18 text

Slide 19

Slide 19 text

Slide 20

Slide 20 text

Slide 21

Slide 21 text

Slide 22

Slide 22 text

Slide 23

Slide 23 text

Slide 24

Slide 24 text

Slide 25

Slide 25 text

Slide 26

Slide 26 text

Slide 27

Slide 27 text

Slide 28

Slide 28 text

Slide 29

Slide 29 text

Slide 30

Slide 30 text

Slide 31

Slide 31 text

Slide 32

Slide 32 text

Slide 33

Slide 33 text

Slide 34

Slide 34 text

Slide 35

Slide 35 text

Slide 36

Slide 36 text

Slide 37

Slide 37 text

Slide 38

Slide 38 text

Slide 39

Slide 39 text

Slide 40

Slide 40 text