In the new remote-first and hybrid workplace, many organizations are struggling to catch up with new tooling and ways of working. Many are discovering for the first time that the physical office was covering up poorly defined teams and poorly defined areas of focus, threatening their DevOps transformation efforts and the overall health and success of their business.
Matthew Skelton and Manuel Pais, coauthors of the highly successful Team Topologies, provide proven patterns for a successful remote-first approach to teams. Using simple tools for dependency tracking and patterns from Team Topologies, such as the Team API, organizations will find that well-defined team interactions are key to effective IT delivery in the remote-first world.
This workbook explores several aspects of team-first remote work,
•How the new “remote-first� world is highlighting existing poor team interactions within organizations.
•Why organizations should use the Team API pattern to define and communicate the focus of teams.
•How organizations can track and remove team-level dependencies.
•How and why organizations should design inter-team communications consciously.
•How and why organizations can use the three team interaction modes from Team Topologies (collaboration, x-as-a-service, and facilitating) to help.
The ideas and patterns presented here will help your organization become more effective with a team-based, remote-first approach to building and running software systems.
Team Topologies was an instant classic. RTIW isn't (unfortunately).
Why so?
Well, TT has introduced great mental models (for both team roles and interaction/dependencies between them) - these resonated with people as nearly everyone was able to easily map their needs and concerns onto those models. RTIW doesn't bring anything particularly new - the goal is to help you to introduce TT within your organization.
The book is very short and rather ... uninspired. I mean - the ideas and practices aren't really revealing. TBH I expected something slightly different - a bunch of case studies that present how TT have been implemented (consciously or not) within various organizations: what were the challenges, what were the side effects, what one had to look at (and avoid), etc.
To be absolutely frank, I haven't noticed a single new idea or an "a-ha" moment. No, I'm not claiming I'm that brilliant :) I think the authors have identified an interesting idea for the book, but they've struggled with codifying the knowledge that would be re-usable for someone else.
OK, is it worth my (your?) money then? TBH, I don't think so (with all the respect to the authors). Stick to the original TT - it should be more than enough.
Unfortunately not worth the time. This is a very short book (~60 pages)
I loved Team Topologies for all the mental models that the original book established, but I’m afraid this book brings little to the table, especially if you’ve already spend some time with TT and the expanded resources available on GitHub.
In fact it feels like the authors simply packaged things up that could be found for a while there (Team API, dependency management exercise, etc) and only slightly rebranded them into the remote context.
I had expected some more in depth case studies, but the ones that are included are very high level.
Nice extension to Team Topologies with some interesting insights from other companies. But I would not expect any mind-blowing insights. If you read and understood Team Topologies, then you most-likely always us the team types, interaction modes, cognitive load evaluation and team boundaries to optimize for flow within your company.
But as the book is really short and the exercises are good points for reflection, I would recommend the book 👍
Tiny book. It's too little for people who already do remote work and it's too much for people who want to start doing remote work. It does have some good beginner tips there, but if the focus was beginners then the book could have been structured to be more beginner friendly and action oriented, with less jargon and complex concepts (topologies part).
Very short book that does not add much. The content is good and relevant, however it is not easy to understand without the basics from Team Topologies and looking at other references (articles and other books properly indicate). It gives a good list of next steps on how to start practicing.
I loved Team Topologies, but didn't really get anything new from this book. It's only 60 pages, so I had hoped for very focused content that expanded the TT ideas, but I got nothing new from this.
Read Team Topologies and "Sooner, Safer, Happier" instead
It is a shorter and summarized version of the original book called Team Topologies. It helps to understand the people about cognitive loads of the team members and the root causes of lack. The `remote` keyword in the title is just marketing, I would say :)
Useless without reading Team Topologies first. Also, pretty small 65 pages or so. Have a few good quotes and references. Other than that doesn't worth much.
Doesn't add much concrete information in the (nearly) 60 pages. The authors spend more time promoting their other book then providing details of the mentioned case studies.
Good addition and addendum to the original book and concept. I've seen the authors talk on this topic and it's nice to have an organized and structured workbook to go with the ideas and approaches. Variable for anyone trying to improve remote team communications and interactions.
In my opinion, a good understanding of the first book "Team Topologies" it's enough, This one has some remote tips... Definitely I will suggest to pick only one between them