Summary of Matthew Skelton & Manuel Pais' Team Topologies

By IRB Media

Get the Summary of Matthew Skelton & Manuel Pais' Team Topologies in 20 minutes. Please note: This is a summary & not the original book. Original book introduction: In Team Topologies DevOps consultants Matthew Skelton and Manuel Pais share secrets of successful team patterns and interactions to help readers choose and evolve the right team patterns for their organization, making sure to keep the software healthy and optimize value streams.

• Language: English
• Publisher: IRB Media
• Release date: Dec 10, 2021
• ISBN: 9781669343783

IRB Media

With IRB books, you can get the key takeaways and analysis of a book in 15 minutes. We read every chapter, identify the key takeaways and analyze them for your convenience.

Book preview

Insights on Matthew Skelton and Manuel Pais's Team Topologies

Contents

Insights from Chapter 1

Insights from Chapter 2

Insights from Chapter 3

Insights from Chapter 1

#1

The author believes that the way technology is being developed and structured in companies today requires a completely different way of thinking and organizing teams.

#2

The problem with taking the org chart at face value is that we end up trying to architect people as if they were software, neatly keeping their communication within the accepted lines. But people don’t restrict their communications to those connected lines on the chart.

#3

The traditional organization chart is outdated the moment work begins. It does not reflect the actual patterns of communication in an organization, and does not take into account the overall flow of work.

#4

The Team Topologies approach acknowledges the importance of informal and value creation structures. By empowering teams, and treating them as fundamental building blocks, individuals inside those teams move closer together to act as a team rather than just a group of people.

#5

In order to be effective, teams require structure. But modern software systems demand a different type of structure than the traditional organization chart. Teams need adaptability and growth, which is not provided by a single, static structure.

#6

The Team Topologies approach provides a consistent, actionable guide for evolving team design to continuously cope with technology, people, and business changes. It recognizes that different teams require different structures to be effective, and that each team has a limited cognitive capacity that must be respected.

#7

Conway’s law states that organizations that create systems are constrained to produce designs that are copies of the communication structures of these organizations. This is because software is based on communication structures.

#8

Conway’s law states that the complexity of a system is in direct proportion to the number of people who have to know about it, understand it, and agree to work with it. This is because no one person can be an expert in all the different facets of

Reviews for Summary of Matthew Skelton & Manuel Pais' Team Topologies

[Joe S · Rating: 3 out of 5 stars]

All bulleted with little continuity. A condensed version would be much more useful. A number of undefined terms used.