Team Topologies¶
Skelton, M., & Pais, M. (2019). Team Topologies: Organizing Business and Technology Teams for Fast Flow.
Cited by¶
2 citations across 2 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Conway's Law
- Start with a single engineering organization of four teams — Auth, Billing, Catalog, Search — that historically sat in one room and shipped a monolith: one codebase, tightly coupled across all four domains, because the producer-graph was densely connected (everyone talked to everyone, so every cross-domain interface was cheap to negotiate and none was enforced).
This sourceDevelops the inverse Conway maneuver and the distributed-monolith failure mode — re-cutting team boundaries to make the desired service architecture arise as the producer-graph's image. (
- Start with a single engineering organization of four teams — Auth, Billing, Catalog, Search — that historically sat in one room and shipped a monolith: one codebase, tightly coupled across all four domains, because the producer-graph was densely connected (everyone talked to everyone, so every cross-domain interface was cheap to negotiate and none was enforced).
Mechanisms¶
- Ownership Boundary Refactor
- It restores the recurring principle that one cohesive component should have exactly one owning team, which cuts the standing coordination cost of split or absent ownership.
This sourceAssigns a cohesive bounded component to one owning team.
- It restores the recurring principle that one cohesive component should have exactly one owning team, which cuts the standing coordination cost of split or absent ownership.
Verification¶
This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.
Links previously used in the corpus¶
Before the registry existed this work was also linked 1 other way.
Registry ID ref:ac17b1535cd3 · see in the full table