Team Topologies: Organizing Business and Technology Teams for Fast Flow

Team Topologies: Organizing Business and Technology Teams for Fast Flow

Taschenbuch
4.01

Durch das Verwenden dieser Links unterstützt du READO. Wir erhalten eine Vermittlungsprovision, ohne dass dir zusätzliche Kosten entstehen.

Beschreibung

"This book will help executives and business leaders focus on the key strategies of high performance teams to effectively address the needs of today and the evolving landscape of tomorrow.” ―Barry O'Reilly, author of Unlearn and Lean Enterprise
Companion book Remote Team Interactions Workbook now available!

Effective software teams are essential 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 is a model that treats teams as the fundamental means of delivery, where team structures and communication pathways are able to evolve with technological and organizational maturity.

In Team Topologies, IT consultants Matthew Skelton and Manuel Pais share secrets of successful team patterns and interactions to help readers choose and evolve the right team patterns for their organization, making sure to keep the software healthy and optimize value streams.

Team 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 and more sustainable, turning inter-team problems into valuable signals for the self-steering organization.
Haupt-Genre
N/A
Sub-Genre
N/A
Format
Taschenbuch
Seitenzahl
216
Preis
22.03 €

Beiträge

1
Alle
4

Well, this was a nice deep dive into Conway's Law. Apart from the well known sentence, I didn't even know that this is an actual part of a more deeper work and analysis. Generally the statement the team topology is part of the software architecture is interesting, especially when you consider all the ideas how a proper team is assembled and what roles there should be in it. Also the ideas of the different teams and their communication is interesting, somehow known from project work and still a bit difficult to grasp.

Beitrag erstellen