Slide 1

Slide 1 text

@kenny_baas @[email protected] Autonomy, is that what we really want? What we really really want? @EvelynvanKelle

Slide 2

Slide 2 text

@kenny_baas @[email protected] @EvelynvanKelle

Slide 3

Slide 3 text

@kenny_baas @[email protected] Autonomy, as described by Mr. Pink, is the urge to direct one's own life. Without the ability to control what, when, and how we work, and who we work with, we'll never be completely motivated to complete a task @EvelynvanKelle

Slide 4

Slide 4 text

@kenny_baas @[email protected] “Man is born free, but one of the first things he learns is to do as he is told and he spends the rest of his life doing that. Thus his first enslavement is to his parents. He follows their instructions forevermore, retaining only in some cases, the right to choose his own methods and consoling himself with an illusion of autonomy.” — Eric Berne @EvelynvanKelle

Slide 5

Slide 5 text

@kenny_baas @[email protected] Definition of autonomy The quality or state of being self-​ governing especially : the right of self-​ government The territory was granted autonomy. Self-​ directing freedom and especially moral independence personal autonomy A self-​ governing state Autonomy Has Origins in Law Since nomos is Greek for "law", something autonomous makes its own laws. The amount of autonomy enjoyed by French-​ speaking Quebec, or of Palestinians in certain towns in Israel, or of independent-​ minded regions of Russia, have become major issues. The autonomy of individual states in the United States has posed serious constitutional questions for two centuries. The autonomy of children is almost always limited by their parents. But when those parents are elderly and begin driving poorly and getting confused about their finances, their children may see the need to limit their autonomy in much the same way. 1. 2. 3. Source: https://www.merriam-​ webster.com/dictionary/autonomy @EvelynvanKelle

Slide 6

Slide 6 text

@kenny_baas @[email protected] http://ueberproduct.de/ep-22-​ jabe-​ bloom-​ marc-​ burgauer-​ designing-​ systems-​ pt-​ ii/ “I hate the word autonomy. ... I think autonomy is individuating. ... The way I hear the word and I think other people hear it – and I might be wrong and other people hear it differently – but the way I hear it is “I have the right to make my own decisions. I have the right to make my own rules.” — Jabe Bloom @EvelynvanKelle

Slide 7

Slide 7 text

@kenny_baas @[email protected] Autonomy can be compulsive Photo by Viktor Mui on Flckr @EvelynvanKelle

Slide 8

Slide 8 text

@kenny_baas @[email protected] Photo by Etienne Girardet on Unsplash @EvelynvanKelle

Slide 9

Slide 9 text

@kenny_baas @[email protected] Positive effect from 100% side L Positive effect from 100% side R Negative effect from 100% side R Negative effect from 100% side L Conformism Autonomy Polarity map - based on Barry Johnsons work Uniqueness Connectedness Sameness Isolation @EvelynvanKelle

Slide 10

Slide 10 text

@kenny_baas @[email protected] Photo by Martin Rancourt on Unsplash Autonomy on several levels of scope > Code > Within teams > Between teams > Organisational @EvelynvanKelle

Slide 11

Slide 11 text

@kenny_baas @[email protected] Autonomy in code No silver bullets and golden hammers Photo by James Harrison on Unsplash @EvelynvanKelle

Slide 12

Slide 12 text

@kenny_baas @[email protected] @EvelynvanKelle

Slide 13

Slide 13 text

@kenny_baas @[email protected] https://martinfowler.com/articles/2021-​ test-​ shapes.html @EvelynvanKelle

Slide 14

Slide 14 text

@kenny_baas @[email protected] @EvelynvanKelle

Slide 15

Slide 15 text

@kenny_baas @[email protected] Users and stakeholders Code Stream-​Aligned Team Tests Domain Model Other people possibly involved in designing and building software Managers Architects User researcher ..... @EvelynvanKelle

Slide 16

Slide 16 text

@kenny_baas @[email protected] @EvelynvanKelle

Slide 17

Slide 17 text

@kenny_baas @[email protected] Positive effect from 100% side L Positive effect from 100% side R Negative effect from 100% side R Negative effect from 100% side L Feeling secure to change the code Cascading changes Sociable Solitary Test in isolation Fast feedback on failure Failure of bug in other class Slower feedback on failure Coherent testing No Mocking coupling Cascading changes on mock/stub Loss of "unit of work" cohesiveness Polarity map - based on Barry Johnsons work @EvelynvanKelle

Slide 18

Slide 18 text

@kenny_baas @[email protected] Autonomy within teams Individuals and interactions over processes and tools @EvelynvanKelle

Slide 19

Slide 19 text

@kenny_baas @[email protected] Like me, please Photo by Judith Prins on Unsplash @EvelynvanKelle

Slide 20

Slide 20 text

@kenny_baas @[email protected] Autonomy IS NOT dictatorship Photo by GR Stocks on Unsplash @EvelynvanKelle

Slide 21

Slide 21 text

@kenny_baas @[email protected] Autonomy is not an excuse to hold something against someone Photo by Pop & Zebra on Unsplash @EvelynvanKelle

Slide 22

Slide 22 text

@kenny_baas @[email protected] @EvelynvanKelle

Slide 23

Slide 23 text

@kenny_baas @[email protected] @EvelynvanKelle

Slide 24

Slide 24 text

@kenny_baas @[email protected] Sunken Cost Fallacy: Why change now? We’ve already wasted so much money. Photo by NESA by Makers on Unsplash @EvelynvanKelle

Slide 25

Slide 25 text

@kenny_baas @[email protected] Positive effect from 100% side L Positive effect from 100% side R Negative effect from 100% side R Negative effect from 100% side L Always in a releasable state Bugs, Bugs, Bugs Trunk based Actions/heuristics Signals/observations Signals/observations Actions/heuristics Branch Polarity map - based on Barry Johnsons work Freedom Individual creativity Care for the whole Shared mental model in code team effort Loss of cohesive mental models Excessive conformity Compete to change the same code When this happens we need to take action Ensemble/mob or pair programming @EvelynvanKelle

Slide 26

Slide 26 text

@kenny_baas @[email protected] Autonomy between teams The “Ivory Towers” Photo by Product School on Unsplash @EvelynvanKelle

Slide 27

Slide 27 text

@kenny_baas @[email protected] Home delivery ordering Takeout Customer Select products for home delivery Know delivery time Legend / Key User Need capability External capability User Depends on Process Software System Make an order for home delivery Pay For home delivery order Home delivery Fulfilment Restaurant employee Accept order Request food deliverer for a specific time Prepare order for home delivery Hand over order to deliverer Takeout Customer When does my delivery arrive? What orders do I need to prepare Food Deliverer Deliver food teamtopologies.… Exploring team and service boundaries with User Needs Mapping - Team Topologies User Needs Mapping refers to the first four steps of the Wardley Mapping process that can provide significant value when helping understand users/customers, their needs and the dependencies required to deliver those needs within an organization. By mapp… Stream-​ aligned team @EvelynvanKelle

Slide 28

Slide 28 text

@kenny_baas @[email protected] Takeout app Home delivery ordering Takeout Customer Select products for home delivery Know delivery time Legend / Key User Need capability External capability User Depends on Process Software System Make an order for home delivery Pay For home delivery order Home delivery Fulfilment Restaurant employee Accept order Request food deliverer for a specific time Prepare order for home delivery Hand over order to deliverer Product page Home delivery order page Payment module Home delivery service restaurant service Payment service Payment provided Restaurant service Delivery broker Takeout app Takeout Customer When does my delivery arrive? What orders do I need to prepare Home delivery service Food delivery services Restaurant backoffice SPA Food Deliverer Deliver food Home delivery service Restaurant service teamtopologies.… Exploring team and service boundaries with User Needs Mapping - Team Topologies User Needs Mapping refers to the first four steps of the Wardley Mapping process that can provide significant value when helping understand users/customers, their needs and the dependencies required to deliver those needs within an organization. By mapp… Stream-​ aligned team @EvelynvanKelle

Slide 29

Slide 29 text

Restaurant POS team Home delivery app team @kenny_baas @[email protected] Home delivery app teams Restaurant POS team Payment team Restaurant POS team Home delivery app team restaurant system Takeout app Home delivery ordering Takeout Customer Select products for home delivery Know delivery time Legend / Key User Need capability External capability User Depends on Process Software System Make an order for home delivery Pay For home delivery order Home delivery Fulfilment Restaurant employee Accept order Request food deliverer for a specific time Prepare order for home delivery Hand over order to deliverer Product page Home delivery order page Payment module Home delivery service restaurant service Payment service Payment provided Restaurant service Delivery broker Takeout app Takeout Customer When does my delivery arrive? What orders do I need to prepare Home delivery service Food delivery services Restaurant backoffice SPA Food Deliverer Deliver food Home delivery service Restaurant service teamtopologies.… Exploring team and service boundaries with User Needs Mapping - Team Topologies User Needs Mapping refers to the first four steps of the Wardley Mapping process that can provide significant value when helping understand users/customers, their needs and the dependencies required to deliver those needs within an organization. By mapp… Stream-​ aligned team This is quirky! Quirky, why is delivery broker not with the other team? @EvelynvanKelle

Slide 30

Slide 30 text

@kenny_baas @[email protected] We should be thinking about limiting the size of software, services, and products to the cognitive load that the team can handle. @EvelynvanKelle

Slide 31

Slide 31 text

@kenny_baas @[email protected] Home delivery app team Restaurant POS team Architects / business analyst / .... Flow of change The Takeout Customer wants to know an accurate ETA before completing the order Some Stakeholder H and over Blocker to flow Instead enable the teams through facilitation Flow of change Home delivery app team Restaurant POS team Architecture enabling Facilitating Facilitating Size shows current cognitive load Stream-​ aligned team Enabling team Legend @EvelynvanKelle

Slide 32

Slide 32 text

Architecture enabling Architecture enabling @kenny_baas @[email protected] Flow of change Home delivery app team Restaurant POS team Facilitating Facilitating Evolves to Home delivery app team Restaurant POS team Facilitating Facilitating Stream-​ aligned team Enabling team Legend Data analytics team Complicated Subsystem team Collaboration Flow of change Facilitating @EvelynvanKelle

Slide 33

Slide 33 text

Architecture enabling Architecture enabling @kenny_baas @[email protected] Flow of change Home delivery app team Restaurant POS team Facilitating Facilitating Evolves to Evolves to Home delivery app team Restaurant POS team Facilitating Facilitating Stream-​ aligned team Enabling team Legend Data analytics team Complicated Subsystem team Collaboration Flow of change Home delivery app team Restaurant POS team Data analytics team Flow of change Home delivery app team Restaurant POS team Flow of change Facilitating Xaas Xaas @EvelynvanKelle

Slide 34

Slide 34 text

@kenny_baas @[email protected] Photo by Ismael Bashiri on Unsplash Enabling teams actively avoid becoming “ivory towers”of knowledge, dictating technical choices for other teams to follow. @EvelynvanKelle

Slide 35

Slide 35 text

@kenny_baas @[email protected] Purpose, needs & Problems Value stream: All activities a team performs from understanding the purpose & problem to building that solution without being blocked Solution Feedback Stream-​aligned team: Long-​ term design + build + run (STEWARDSHIP) solving business needs/problems with software-​ enriched services in a small, ~stable team of around ~5-9 people Team first! 💡You DESIGN it, you build it and you run it! Stream aligned teams, should aim to become product teams! @EvelynvanKelle

Slide 36

Slide 36 text

@kenny_baas @[email protected] https://amplitude.com/blog/journey-​ to-​ product-​ teams-​ infographic AKA blockers to flow

Slide 37

Slide 37 text

@kenny_baas @[email protected] Heavily focusses on one of the poles @EvelynvanKelle www.equalexperts.com Three reasons why Equal Experts doesn't recommend the SAFe framework | Equal Experts Equal Experts advises its customers to not use the SAFe framework. Our feedback shows that SAFe doesn't accelerate delivery, satisfy product demand, or create adaptive architectures https://www.equalexperts.com/blog/our-​ thinking/problems-​ with-​ safe-​ framework/

Slide 38

Slide 38 text

@kenny_baas @[email protected] Positive effect from 100% side L Positive effect from 100% side R Negative effect from 100% side R Negative effect from 100% side L Customer centric Ivory tower silo's Collaboration Actions/heuristics Signals/observations Signals/observations Actions/heuristics Isolation Freedom Team Creativity Work ahead of new technology Uniqueness Connectedness synergy of the whole Care for the customer Loss of equality Isolation Selfish Sameness High cognitive load Excessive comformity @EvelynvanKelle

Slide 39

Slide 39 text

@kenny_baas @[email protected] Autonomy in organizations A continuous negotiation Photo by Mike Kononov on Unsplash @EvelynvanKelle

Slide 40

Slide 40 text

@kenny_baas @[email protected] Vision, boundaries, or both? Photo by Annie Spratt on Unsplash @EvelynvanKelle

Slide 41

Slide 41 text

@kenny_baas @[email protected] So, who calls the shots now? Photo by Tingey injury on Unsplash @EvelynvanKelle

Slide 42

Slide 42 text

@kenny_baas @[email protected] Leadership is not Dictatorship It requires us to balance power and Love Photo by Tingey injury on Unsplash @EvelynvanKelle

Slide 43

Slide 43 text

@kenny_baas @[email protected] We gave them autonomy. Why aren’t they doing anything with it? Photo by Lucas van Oort on Unsplash @EvelynvanKelle

Slide 44

Slide 44 text

@kenny_baas @[email protected] When there’s autonomy everywhere, do we still need managers and architects? Photo by Miguel a Amutio on Unsplash @EvelynvanKelle

Slide 45

Slide 45 text

@kenny_baas @[email protected] Positive effect from 100% side L Positive effect from 100% side R Negative effect from 100% side R Negative effect from 100% side L Agency Indecisiveness Centralised decisions Actions/heuristics Signals/observations Signals/observations Actions/heuristics Decentralised decisions Empowering teams Spontaneuous Teams acting decisively Empowering the organisation Organisation can coordinate Organisation acting decisively Everyone feels included Organisation cannot coordinate FOMO and feeling left out Burden of consequences for mistakes Disempowering the teams no creativity or spontaneous Lack of team accountability queues @EvelynvanKelle

Slide 46

Slide 46 text

@kenny_baas @[email protected] Levels of scope By Ruth Malan @EvelynvanKelle

Slide 47

Slide 47 text

@kenny_baas @[email protected] Patterns of autonomy and isolation are fractal. If you find one at one layer, you can bet you can find the same at other layers as well. Photo by Martin Rancourt on Unsplash @EvelynvanKelle

Slide 48

Slide 48 text

@kenny_baas @[email protected] Autonomy, is that what we really (really) want? > Define and negotiate boundaries continuously > Manage polarities @EvelynvanKelle

Slide 49

Slide 49 text

Thank you! @kenny_baas @[email protected] @EvelynvanKelle @EvelynvanKelle @kenny_baas Independent software consultant, tech lead, and software architect @EvelynvanKelle Behavioral change consultant https://collaborative-​ software-​ design.com/