Comparison
Complicated-subsystem teamvsEnabling team
Complicated-subsystem team
the pricing engine needs actual mathematicians, so it has its own team rather than living in everyone's backlog.
A team owning a part of the system that requires specialist knowledge most engineers do not have — a matching engine, a codec, a risk model. It is justified only when the specialism is genuine and rare, because every such team is a dependency for everyone else. It is the type most often claimed and least often warranted, since 'this is complicated' usually means undocumented rather than specialist.
Full entry →Enabling team
two specialists sat with your team for six weeks, taught you the testing approach, and then left.
A team that temporarily works alongside another to raise its capability, then deliberately withdraws. The withdrawal is the defining feature: an enabling team that stays becomes either a dependency or a shadow platform team. It is the structural answer to a skill gap that would otherwise be solved by permanently routing all work of one kind through the same three people.
Full entry →