Forget monoliths vs microservices - focus on Team Cognitive Load - Team Topologies - commercetools and dept - 2020-03-10
0 likes579 views
The document discusses the importance of managing team cognitive load when developing software architectures, particularly between monoliths and microservices. It emphasizes a 'team-first' approach, advocating for smaller service sizes that align with team capacity and well-defined team interactions to enhance operational agility. It also outlines key principles and metrics to measure cognitive load and promote effective collaboration among teams.
![(Intrinsic)
] Extraneous [
Germane
20](https://image.slidesharecdn.com/forgetmonolithsvsmicroservices-focusonteamcognitiveload-teamtopologies-commercetoolsanddept-2020-03--200310132140/85/Forget-monoliths-vs-microservices-focus-on-Team-Cognitive-Load-Team-Topologies-commercetools-and-dept-2020-03-10-20-320.jpg)
Forget monoliths vs microservices - focus on Team Cognitive Load - Team Topologies - commercetools and dept - 2020-03-10
- 1. TeamTopologies.com @TeamTopologies Forget ‘Monoliths vs Microservices’: focus on Team Cognitive Load Matthew Skelton Co-author of Team Topologies @matthewpskelton Commercetools/Dept - 10 March 2020
- 2. 2 Monoliths vs Microservices Team Cognitive Load Case Studies Getting started
- 3. Team Topologies 3 Organizing business and technology teams for fast flow Matthew Skelton & Manuel Pais IT Revolution Press Order via stores worldwide: teamtopologies.com/book
- 5. 5
- 6. “Start with monolith and extract microservices.” - Tammer Saleh 6 https://www.infoq.com/presentations/cloud-anti-patterns
- 7. “Don’t start with a monolith when your goal is a microservices architecture” - Stefan Tilkov 7 http://martinfowler.com/articles/dont-start-monolith.html
- 8. “If you can't build a monolith, what makes you think microservices are the answer?” - Simon Brown 8 http://www.codingthearchitecture.com/2014/07/06/distributed_big_balls_of_mud.html
- 9. 9 WTF?!?! * where to focus?
- 10. “Software that fits in your head” - Daniel Terhorst-North 10 https://speakerdeck.com/tastapod/microservices-software-that-fits-in-your-head?slide=62
- 11. 11 “Software that fits in our heads”
- 12. 4 key metrics: ‘Accelerate’ 12 lead time deployment frequency mean time to restore (MTTR) change fail percentage
- 13. Software that is ‘too big for our heads’ works against organizational agility 13
- 15. COGNITIVE LOAD: The total amount of mental effort being used in the working memory - John Sweller 15
- 17. Intrinsic Extraneous Germane 17 “How do I deploy this app, again?”
- 19. Intrinsic (skills) Extraneous (mechanism) Germane (domain focus) 19
- 21. More: ‘Hacking Your Head’ 21 Jo Pearce (@jdpearce) https://www.slideshare.net/JoPearce5/hacking-your-head-managing-information-overload-extended
- 22. Limit the size of software services/products to the cognitive load that the team can handle. 22
- 23. 23 “Software that fits in our heads”
- 24. A ‘team-first’ approach to software boundaries 24
- 25. Team size ≲ 9 * * possibly 15 25
- 26. 26 Each service must be fully owned by a team with sufficient cognitive capacity to build and operate it.
- 32. 4 fundamental topologies 32 Stream-aligned team Enabling team Complicated Subsystem team Platform team
- 33. 4 fundamental topologies 33 Flow of change
- 35. 35 Team Interactions 3 defined Interaction Modes
- 36. 36 Team Interactions Collaboration: 2 teams working together
- 37. 37 Team Interactions X-as-a-Service: 1 provides, 1 consumes
- 38. 38 Team Interactions Facilitating: 1 team helps another
- 39. 39 Team Interactions 3 defined Interaction Modes Collaboration: 2 teams working together X-as-a-Service: 1 provides, 1 consumes Facilitating: 1 team helps another @matthewpskelton / @TeamTopologies
- 40. 3 core interaction modes 40 Flow of change X-as-a-Service Facilitating Collaboration
- 41. 41 Rapid flow of change
- 42. 42 Rapid feedback from running systems
- 43. 43
- 44. 44
- 45. 45 Handovers (can) kill flow
- 46. 46 Team ownership must include: Releasability Testability Operability / Supportability
- 47. 47
- 48. 48 → flow of change → →
- 49. 49
- 50. 50
- 51. “...trend analysis, simulations, rapid prototyping, scenario planning, gaming, environmental scanning … give clues to the context and competitive environment.” - Dr. Naomi Stanford, “Guide to Organisation Design” (The Economist) 51
- 52. Case Studies 52
- 53. CaseStudy 53
- 58. Team became too large ⇔ System became monolithic Blocked flow of work across streams 58
- 59. Listen to ‘triggers for evolution’ ❏ Software grows too large ❏ Over specialization (Brent) ❏ Increased coordination needs 59
- 60. CaseStudy 60
- 63. It’s not always about software size... More broadly, align size and number of domains of responsibility with team cognitive capacity. 63
- 64. Aim for teams with high cohesion internally (think autonomy, mastery & purpose) Aim for low bandwidth comms between smaller teams 64
- 65. Listen to ‘triggers for evolution’ ❏ Awkward interactions ❏ People not invested, burn out ❏ Frequent context switching 65
- 66. Getting started with team cognitive load 66
- 67. How well can the team as a unit “grok” the systems they own and develop? Explicit cognitive load 67
- 68. Push some things into a Platform? Explicit cognitive load 68
- 69. Are skills or capabilities missing? Explicit cognitive load 69
- 70. What would change if we adopted the 3 team interaction patterns? Collaboration, X-as-a-Service, Facilitating Team Interactions 70
- 71. Collaboration, X-as-a-Service, Facilitating How would teams react & behave? Team Interactions 71
- 72. How is your Platform defined? Thinnest Viable Platform 72
- 73. What is the thinnest platform that could work? Thinnest Viable Platform 73
- 74. What’s needed to run and support it? Thinnest Viable Platform 74
- 75. Team Topologies 75 Organizing business and technology teams for fast flow Matthew Skelton & Manuel Pais IT Revolution Press Order via stores worldwide: teamtopologies.com/book
- 76. Training 76 Day 1 Fundamentals Day 2 Deep Dive Day 3 Applying in Context teamtopologies.com/training
- 77. Looking for case studies 77 Global manufacturing company Large government agency Global financial services
- 78. Remaining problems 78 Measuring cognitive load at scale Assessing team communication at scale How to nudge managers and heads of X to become Team Topologies enablers
- 79. TeamTopologies.com @TeamTopologies Sign up for news and tips: TeamTopologies.com
- 80. Thank you! teamtopologies.com 80 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