Download as PDF, PPTX
Uploaded byMatthew Skelton
Beyond the Spotify model - Team Topologies - DevTestNorth - 2019-09-25 - Matthew Skelton
The document discusses the limitations of the Spotify model for team design in software delivery, highlighting its benefits in promoting team collaboration and responsibilities, while also recognizing its shortcomings. It introduces the concept of team topologies, derived from extensive research, which aims to enhance organizational flow and support cognitive load management. The document outlines foundational team interaction patterns and emphasizes a team-first mindset for efficient organizational evolution.
More Related Content
![Rick Austin - Portfolio mangement in an agile world [Agile DC]](https://cdn.slidesharecdn.com/ss_thumbnails/portfoliomangementinanagileworld-agiledc-181015223517-thumbnail.jpg?width=640&height=640&fit=bounds)
![[JAZUG Tohoku Azure DevOps] Azure DevOps](https://cdn.slidesharecdn.com/ss_thumbnails/20181130jazugsendaiazuredevops-181201031328-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to Beyond the Spotify model - Team Topologies - DevTestNorth - 2019-09-25 - Matthew Skelton
Beyond the Spotify model - Team Topologies - DevTestNorth - 2019-09-25 - Matthew Skelton
- 1. TeamTopologies.com @TeamTopologies Beyond the Spotifymodel using Team Topologies for fast flow and organisation evolution Matthew Skelton, Conflux co-author of Team Topologies - @matthewpskelton DevTest North, Leeds - 25 Sept 2019
- 2.
- 3. 3 The Spotify Model Limitations TeamTopologies Getting started
- 4.
- 5.
- 6. The Spotify modelof team design for software delivery 6
- 7. 7 Henrik Kniberg &Anders Ivarsson, 2012 https://blog.crisp.se/wp-content/uploads/2012/11/SpotifyScaling.pdf
- 8. 8 The Spotify model Squad:semi-autonomous delivery team Tribe: family of Squads - related work Chapter: line management within a Tribe Guild: cross-Tribe interest/specialist group
- 9. 9 The Spotify modelhas been hugely helpful to 100s of organizations
- 10. The Spotify model helpsto... 10
- 11.
- 12.
- 13. 13 Promote good kinds ofteam collaboration
- 14. 14 Plan and budget forcross-team enablers
- 15. 15 The Spotify modelhelps to Encourage flow of change Establish and clarify team responsibilities Promote good kinds of team collaboration Plan and budget for cross-team enablers @matthewpskelton / @TeamTopologies
- 16. Limitations of the Spotifymodel 16
- 17. “This article isonly a snapshot of our current way of working - a journey in progress, not a journey completed. By the time you read this, things have already changed.” - Kniberg & Ivarsson 17
- 18. There is NoSpotify Model 18 Marcin Floryan, 2016 https://www.infoq.com/presentations/spotify-culture-stc
- 19.
- 20.
- 21.
- 22.
- 23. 23 We also needto address Software sizing and cognitive load Heuristics for Conway’s Law Patterns for team interactions Triggers for change and evolution @matthewpskelton / @TeamTopologies
- 24.
- 25. topology the way inwhich constituent parts are interrelated or arranged Greek: τοπολογία (τόπος == ‘place’) 25
- 26. Team Topologies 26 Research over5 years across multiple industry sectors Informed by 50+ peer-reviewed journal articles 30+ client organizations - consulting and training since 2013 with orgs in CN, EU, IN, US, UK, + Book: 12+ case studies from well-known organizations
- 27. Origins - DevOpsTopologies 27 CC BY-SA devopstopologies.com @matthewpskelton / @TeamTopologies
- 28. 28 Philip Fisher-Ogden, Director ofEngineering at Netflix: “thanks for your insightful articulations of devops topologies. They inspired many discussions and helped us to think about what model Netflix teams could be/are using.” https://twitter.com/philip_pfo/status/999074792123740160
- 29. 29 Crystal Hirschorn, Director ofEngineering at Condé Nast International “Your topological models resonated extremely well on both the Dev and Ops side btw! I like the balanced arguments, e.g. different perspectives, for each pattern.” https://twitter.com/cfhirschorn/status/1103387659890819073
- 30. Team Topologies 30 Organizing businessand technology teams for fast flow Matthew Skelton & Manuel Pais Publication date: Sept 2019 IT Revolution Press Pre-order from Amazon: https://teamtopologies.com/book
- 31. 💥#1 on Amazon Businessand Organizational Learning 31
- 32. “innovative tools andconcepts for structuring the next generation digital operating model” Charles T. Betz, Principal Analyst, Forrester Research 32
- 33. Team Topologies forfast flow Conway’s Law Team-first Thinking Team Interactions Sensing for Evolution 33
- 34.
- 35.
- 36. 36 Team-first Thinking The teamis the means of delivery
- 37. 37 Team-first Thinking Design forteam cognitive load
- 38. 38 Team-first Thinking Choose boundariesfor team ownership
- 39. 39 Team-first Thinking Physical anddigital workspace
- 40. 40 Team-first Thinking The teamis the means of delivery Design for team cognitive load Choose boundaries for team ownership Physical and digital workspace @matthewpskelton / @TeamTopologies
- 41.
- 42.
- 43. 43 Conway’s Law Heuristic for‘natural’ expected design
- 44. 44 Conway’s Law Mirroring intech system + human system
- 45. 45 Conway’s Law Reverse Conwayto mitigate worst effects
- 46. 46 Conway’s Law Constraint onsolution search space
- 47. 47 Conway’s Law Heuristic for‘natural’ expected design Mirroring in tech system + human system Reverse Conway to mitigate worst effects Constraint on solution search space @matthewpskelton / @TeamTopologies
- 48.
- 49.
- 50. 50 Team Interactions 3 definedInteraction Modes
- 51. 51 Team Interactions Collaboration: 2teams working together
- 52. 52 Team Interactions X-as-a-Service: 1provides, 1 consumes
- 53. 53 Team Interactions Facilitating: 1team helps another
- 54. 54 Team Interactions 3 definedInteraction Modes Collaboration: 2 teams working together X-as-a-Service: 1 provides, 1 consumes Facilitating: 1 team helps another @matthewpskelton / @TeamTopologies
- 55. 4 fundamental topologies 55 Stream-alignedteam Enabling team Complicated Subsystem team Platform team
- 56. 4 fundamental topologies 56 Flowof change
- 57. 3 core interactionmodes 57 Flow of change X-as-a-Service Facilitating Collaboration
- 58.
- 59.
- 60. 60 Sensing for Evolution Notall teams in the org look the same
- 61. 61 Sensing for Evolution Discover,then push to Platform
- 62. 62 Sensing for Evolution Awkwardteam interactions are signals
- 63. 63 Sensing for Evolution Evolvethe org with changing ecosystem
- 64. 64 Sensing for Evolution Notall teams in the org look the same Discover, then push to Platform Awkward team interactions are signals Evolve the org with changing ecosystem @matthewpskelton / @TeamTopologies
- 65. Getting started with theTeam Topologies approach 65
- 66. Getting started 66 Explicit cognitiveload Large Conway mismatches Team Interactions Thinnest Viable Platform
- 67. How well canthe team as a unit “grok” the systems they own and develop? Push some things into a Platform? Are skills or capabilities missing? Explicit cognitive load 67
- 68. Getting started 68 Explicit cognitiveload Large Conway mismatches Team Interactions Thinnest Viable Platform
- 69. Are there majormismatches between the team interactions and the required software / system architecture? What could be easily adjusted? Large Conway mismatches 69
- 70. Getting started 70 Explicit cognitiveload Large Conway mismatches Team Interactions Thinnest Viable Platform
- 71. What would changeif we adopted the 3 team interaction patterns? Collaboration, X-as-a-Service, Facilitating How would teams react & behave? Team Interactions 71
- 72. Getting started 72 Explicit cognitiveload Large Conway mismatches Team Interactions Thinnest Viable Platform
- 73. How is yourPlatform defined? What is the thinnest platform that could work? What’s needed to run an support it? Thinnest Viable Platform 73
- 74. Getting started 74 Explicit cognitiveload Large Conway mismatches Team Interactions Thinnest Viable Platform
- 75.
- 76. 76 The Spotify modelhelps to Encourage flow of change Establish and clarify team responsibilities Promote good kinds of team collaboration Plan and budget for cross-team enablers @matthewpskelton / @TeamTopologies
- 77. 77 We also needto address Software sizing and cognitive load Heuristics for Conway’s Law Patterns for team interactions Triggers for change and evolution @matthewpskelton / @TeamTopologies
- 78. Team Topologies forfast flow Conway’s Law Team-first Thinking Team Interactions Sensing for Evolution 78
- 79. Getting started 79 Explicit cognitiveload Large Conway mismatches Team Interactions Thinnest Viable Platform
- 80. Team Topologies 80 Organizing businessand technology teams for fast flow Matthew Skelton & Manuel Pais Publication date: Sept 2019 IT Revolution Press Pre-order from Amazon.com: https://teamtopologies.com/book
- 81. Training 81 Day 1 Fundamentals Day 2 DeepDive Day 3 Applying in Context teamtopologies.com/training
- 82. Team Topologies Fundamentals 26 Sept2019, Leeds, UK Details: teamtopologies.com run by: hosted by: with Matthew Skelton 1-day training course Photo:JaxDevOps
- 83.
- 84. Sign up fornews and tips: TeamTopologies.com 84
- 85. Thank you! teamtopologies.com 85 Matthew Skelton,Conflux @matthewpskelton Manuel Pais, Independent @manupaisable Copyright © Conflux Digital Ltd 2018-2019. All rights reserved. Registered in England and Wales, number 10890964 Icons made by Freepick from www.flaticon.com - used under license
- 86.