Gre

Overall this book makes sense. It just need to be more concise. However, I understand the authors were trying to let people pick certain chapters without missing some information but to readers who read the whole book, it is kind of redundant. I bet Conway's law shows up like 50 times. J/K

Excellent book.

This book talks about organizational design for technical teams and breaks teams into specific types or functions: stream-aligned teams, enabling teams, complicated subsystem teams and platform teams. It also talks about the importance of paying attention to cognitive load on teams. I’ve been diffusing this book in my organization as it is a great way to think about how we work together and how we might want to evolve our team structures and why. We have started to use this vocabulary as well and it’s a great shared mental model.

The book contains too many misrepresentation of existing views and evidence. Two concepts are quite fundamental to the rest of the book: Conway's Law and cognitive load.

The Conway's Law is explained as if one must align architecture to teams' structure, while the message of the law is quite the opposite: seek a flexible organization since future architecture will change. The book does mention flexibility, but only in communication structures, which although useful, doesn't bring meaningful flexibility to meet the changing needs.

Cognitive load is in rather unclear way relabeled and redefined into team cognitive load, still giving impression of being the same thing (due to strangely still using "cognitive load" term while meaning "team cognitive load". The second term is actually not cognitive load anymore, but rather self-invented (without proper backing from any research) for the purpose of justifying that teams should not share ownership of services / components / code.

Especially this aspect of code ownership is heavily disputed by countless organizations where teams do share code ownership without feeling of being overwhelmed (the book mistakenly uses "cognitively overloaded" as a term for this feeling).

At the end, the book heavily falls short of proper analysis of real problems like teams feeling overwhelmed by complexity.

This is an excellent book, a must read for any IT Engineer and manager

Hay pocos cambios respecto de la primera edición, pero las nuevas aportaciones lo enriquecen bastante.

Un must ! Les éléments indiqués dans ce livre sont une mine d'or quand on doit opérer des ajustements dans une organisation IT dans l'agilité et en permettant la création de flux de valeur sans coutures.

Great continuation and follow up on first edition

Excellent