Book/Team-Topologies

Model: 3 horizons of software development Horizon 1 covers the immediate future with products and services that will deliver results the same year; Horizon 2 covers the next few periods, with an expanding reach of the products and services; and Horizon 3 covers many months ahead, where experimentation is needed to assess market fit and suitability of new services, products, and features. (origin: Book: Lean Enterprise - Jez Humble & Joanne Molesky & Barry O’Reilly) (src: [[book-team-topologies-matthew-skelton-manuel-pais....

Model: Brooks law adding new people to a project doesn't immediately increase its capacity in fact, it quite possibly reduces capacity during an initial stage ramp-up period necessary to bring people up to speed, communication lines inside the team also increase significantly with every new member. emotional adaptation required both from new and old team member (the storming stage of Model_ Tuckman’s Performance Model) (origin: Book_ The Mythical Man-Month - Frederick Brooks) (src: [[book-team-topologies-matthew-skelton-manuel-pais....

Humans can only manage about 150 relationships Even online (src: Video_ Start With Why - Simon Sinek) inner circle 3-5 very close friends or family members sympathy group 7-10 close friends who care about each other’s fate hunting group 30-50 collegues who care about each other’s fate-how much it takes to achieve a goal clan 100-150 people who maintain stable inter-personal relationships-everybody knows eachother-peer pressure works tribe 500-2500 people who speak the same language or dialect (src: [[video-the-scaling-dilemma-mary-poppendieck....

(src: Book_ Team Topologies - Matthew Skelton & Manuel Pais) Each stage has it’s own common feelings behaviors team tasks The feelings and behaviours are useful for recognizing which stage you’re in. And to confirm that it is completely okay to feel and behave this way! (src: Article: Using the Stages of Team Development _ MIT Human Resources)

Model: required vs actual communication ideal: required level of communication = actual level of communication often: mismatch between required level of communication actual level of communication solution A) increase actual communication solution B) decrease required communication ««< = Team Topologies todo: illustration (notebook p60): y axis: how much communication x axis: nothing / 2 different approaches src: Session_ Team Topologies origin: Matthew Butt

types stream aligned (“feature team”) enabling teams (experts, coaches) platform team complicated subsystem (eg. image recognitions) Interactions (collaboration modes) collaboration (looks like 1 team) acts as a service (platform -> stream aligned) facilitating why? size of team cognitive load reverse Conway maneuver looking for low-bandwidth communication Model_ required vs actual communication Model_ pioneers, settlers, town planners (ref: Book_ Team Topologies - Matthew Skelton & Manuel Pais) (src: Conference_ SocratesBE 2022)