F them and worked for over a decade in nvironments where this isn t true making it hard to continue the rest of the book They also argue that teams should be separated on purpose and only coordinate with the designated interaction mode which is the Spirit of the Wolf exact opposite of thenvironments that I A Vineyard Christmas enjoyed working most where interaction between teams was freuent and informal In myxperience this level of ownership
And Separation Is Going To Cause Silo Forming And Will separation is going to cause silo forming and will building one product really hard I would recommend against thisThe rest of the book xplores the four team topologies stream aligned teams nabling teams complicated sub system teams and platform teams Of these the authors recommend most teams ought to be stream aligned and I would agree with that That said many stream aligned teams in the same product would likely need to work
ON THE SAME SERVICESCOMPONENTS YET THE AUTHOR SEEMS TO the same servicescomponents yet the author seems to that this isn t the case as good modular architecture can solve that Here my world must be very different from the authors as I do not see how this can be resolvedThe last part xplores the three team interaction modes 1 collaboration 2 x as a service and 3 facilitating The different kind of teams have different default interaction modes Again I found the recommendations against non standard team interaction uite harmfulAll in all as said this is a difficult book to read and review I learned from it I liked it at times it was vebose but written ok yet I would never recommend it to anyone with the xception of people who want to learn about what is the opposite of multiple teams interacting closely on shared code For this reason in the nd I decided on two star. Ization making sure to keep the software healthy and optimize value streamsTeam Topologies is a major step forward in organizational design for software presenting a well defined way for teams to interact and interrelate that helps make the resulting software architecture clearer andsustainable turning inter team problems into valuable signals for the self steering organizati. ,
review Team Topologies: Organizing Business and Technology Teams for Fast FlowRather than giving me new knowledge I am now reading it through the lens of my new company and how they are organized and I am riveted The business unit I am in is Conway s law amplified and the book is giving me the words to be able to communicate the problems and why I m looking at the communications and dependency overhead and inside I am screaming look at the software architecture And break up the DB and Ops silo I myself am forming a platform X as a Service team for Cloud Native apps that includes CICD containers microservices architecture data
analytics services observability services and using the book to help me designservices observability services and using the book to help me design teams It is a well written and actionable book This book was hard for me to read and hard for me to review It made me angry at times Some of the recommendations of the book almost made me throw it away on the spot Yet I wanted to hear what the authors have to say The further I got in the book the I became to see some value in what they were sharing Yet I would not recommend following the suggestions from this bookThis book is about teams and organizations How should you structure your teams and the organization It proposes four types of teams topologies that you might need to build products Their argument when you make these teams
"Topologies Clear And Specify "clear and specify interaction modes then that should greatly improve your product developmentHowever the whole book stands and falls with their interpretation of Conway s Law and the strict approach to code ownership they take chapter two They see that componentsservices must be owned by teams and the team design must map to the architectural structure Personally I disagree with both Is a model that treats teams as the fundamental means of delivery where team structures and communication pathways are able to volve with technological and organizational maturityIn Team Topologies IT consultants Matthew Skelton and Manuel Pais share secrets of successful team patterns and interactions to help readers choose and volve the right team patterns for their organ.
This book has given words to some team problems I have seen over several years along with ways to fix problems Essential reading for managers stressed out devs and anyone who wants to make software delivery flow better Lots of useful content and references here spread throughout Also some informative diagrams to prompt discussioni did feel however the to prompt discussionI did feel however the content of the book could have been written in 40 pages a lot of repetition and use of academic language when
a simpler conversation style would have There are many great books with wisdom on how best to form ffective teams butsimpler conversation style would have There are many great books with wisdom on how best to form ffective teams but trouble has always been that this folk
"Knowledge Is Widely Distributed "is widely distributed uses different words for the same things What the authors have achieved here is to organise this knowledge in a clear taxonomy of team topologies and interaction patternsWhat s they do a great job of citing other important works on the topic so that the reader can follow ideas back to their source Melvin Conway James Lewis Daniel Pink Evan Bottcher Michael Nygard Nicole Forsgren Jez Humble Gene Kim Allan Kelly John Roberts Don Reinertsen and many are liberally uoted throughout the text That makes this book a great summary work on a topic of vital importance to any software organisation of any size how do we best divide the work so that teams have the best possible chance of success Finally a resource that looks past the agile teams and supporting business facing only products by introducing Enabling and Platform teams I read this book twice The first time I read it I was working at another company and many of the teams were stream aligned and there were platform teams so the book was validation. Effective software teams are ssential for any organization to deliver value continuously and sustainably But how do you build the best team organization for your specific goals culture and needs Team Topologies is a practical step by step adaptive model for organizational design and team interaction based on four fundamental team types and three team interaction patterns It.