To calculate the overall star rating and percentage breakdown by star, we do not use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyses reviews to verify trustworthiness.
This is a great book for people who want to create teams that deliver value. The authors define four types of teams that provide a different set of objectives. They also describe the communication between these teams making it very clear how each type of team operates in relation to each other. The punchy delivery and simple illustrations offer an easy to read resource that is also a great reference to help you establish the team structures needed to deliver value to your customers. I highly recommend this book for those who want to structure their organisation to deliver high value.
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.
Wow. It's the year 2020 and books that elaborate on the importance of teams and thoughtful team design are still ranked high on Amazon. I am in software dev for nearly two decades and during that time there were some seminar books of processes and Teams. I think of Cockburn, Tom de Marco, Nygard and Kent Beck. Those books were thin and still crammed with ground-breaking well formulated ideas.
Many trustworthy people recommended this book to me and am totally disappointed how few ideas I could digest from it. It's full of repetition, lenghty convoluted sentences with many buzzwords and little meaning.
The images and diagrams are colorful. And that's the most positive I can say. Chaotic. Confusing. Vague. I am a single reader, but I tell you. "This is not a book you need to read." The topic is important but you will not learn enough from it. Go find it elsewhere.
Interessantissimo in quanto tratta argomenti direttamente legati alla mia professione. Ottima qualità della carta, contenuti interessanti e referenziati, vengono da esperienze personali e studi degli autori. Ottimi spunti, potrebbero espandere maggiormente ma comunque racconta bene la loro idea e la sua applicabilità.
Was eigentlich jeder weiss: so wie ich die Teams aufstelle, so wird sich dies in meiner Architektur widerspiegeln. Und wie sollen Teams aufgestellt werden, damit der Arbeitsfluss am besten sichergestellt ist? 4 Team Typologien stehen dabei zur Auswahl. Diese gilt es gut überlegt zu kombinieren. Ein MUST-READ für Scrum Master, Product Owner, Architekten und alle, die bei der Teamgestaltung Einfluss nehmen.
A great book on organizing teams, with helpful examples from real life and useful references to other resources (books and research). Some parts seem a bit too academic, but this is not necessarily a bad thing.