The design and UX isn't done, Rob and Abbie, okkurrrr! 😌
lischa3000's review against another edition
2.0
Knowledgeable, but really boring. Felt like reading course material at uni.
kepheus's review against another edition
3.0
This is a quintessential "should have been/stayed a blog post" book. If you want to read this, start with the conclusion and, if you have any questions, backtrack to the relevant section. You likely won't because it's fairly self-evident. For example, narrowing team types and communication styles to a minimal set. Just make sure you pay attention to the part about cognitive load because I've been on very few teams that didn't have this problem.
books_are_nice_and_enjoyable's review against another edition
4.75
 Recommended.
Â
I read this book after reading Sam Newman's Microservices book - he covered some of the ideas included in the book in his coverage, and those ideas seemed important enough for me to decide to read this book in full after I'd finished Newman's coverage.Â
This is an important book you'll probably want to read. The evidence the authors present in favor of their claims is limited and in my view somewhat inadequate, but there are some really important ideas included in this book. The ideas are important in part because people who really ought to know those things ...usually can not be expected to do so, and the fact that they do not have this knowledge will lead to suboptimal outcomes.
Â
I read this book after reading Sam Newman's Microservices book - he covered some of the ideas included in the book in his coverage, and those ideas seemed important enough for me to decide to read this book in full after I'd finished Newman's coverage.Â
This is an important book you'll probably want to read. The evidence the authors present in favor of their claims is limited and in my view somewhat inadequate, but there are some really important ideas included in this book. The ideas are important in part because people who really ought to know those things ...usually can not be expected to do so, and the fact that they do not have this knowledge will lead to suboptimal outcomes.
meelik's review
3.0
A good book for falling asleep...
Essential things are written, unfortunately, in a highly complex tone. The book could benefit from removing bloat and repetitions and changing the language into less academic.
Essential things are written, unfortunately, in a highly complex tone. The book could benefit from removing bloat and repetitions and changing the language into less academic.
caffgeek's review against another edition
5.0
Very good information. A tad repetitive or dry at times, but overall worth it
slayra's review
informative
medium-paced
4.0
I was pleasantly surprised by this book. I was expecting a good idea followed by many pages repeating the same idea using different words (which happens, admittedly), but this book presents many insights to organise software teams from a human perspective. I am a supporter of their views and interpretations, and I'm looking forward to apply this research to my teams.
luckypluto's review
A really boring book about work stuff that I don’t care about.
dunguyen's review
3.0
Team Topologies is about the title, how teams are interrelated and managed. The core of the book is actually pretty simple and outlines a theory and framework. It consists of four types of teams, stream-aligned, platform, enabling, and complicated-subsystems and three types of team interaction models, collaboration, x-as-a-service, and facilitating. With Conway's Law as a guide, that the organizational structure shapes the product that is being built, Skelton and Pais explain how limiting organizational design to four types of teams and three types of team interaction can improve the business to deliver things faster.
I find the core ideas really interesting and have anecdotal experience that it may also really fit with real-world examples so I can recommend the book. At the same time it's not an easy read, mostly because of the overcomplicated explanations and examples that don't add to the comprehension. That along with the lack of actual advice for implementing these distracts a bit. The theory seems sound and I can take this with me, I just wish there was more tangible examples and some guidance to properly implement this.
I find the core ideas really interesting and have anecdotal experience that it may also really fit with real-world examples so I can recommend the book. At the same time it's not an easy read, mostly because of the overcomplicated explanations and examples that don't add to the comprehension. That along with the lack of actual advice for implementing these distracts a bit. The theory seems sound and I can take this with me, I just wish there was more tangible examples and some guidance to properly implement this.
scottwasalreadytaken's review
4.0
This one follows the 85% rule (which I just made up) : 85%of the value could have been expressed in 15% of the words.
Valuable content and insights though. Portions of it will be useful for reference.
Valuable content and insights though. Portions of it will be useful for reference.