One Small Pizza Team Is a New Two Pizza Team

Theorem T3
Engineers without delegation experience accelerate ~3x, not 10x. Coding speeds up ~20x, but coding is only ~30% of end-to-end delivery, so net team acceleration is ~3x. A 3-person micro-team matches the output of a 9-person Scrum team.

The name plays on the two-pizza team rule, but the claim is sharper: a 3-person micro-team now matches a 9-person Scrum team, because engineers without delegation experience accelerate about 3x, not 10x.

Implication

10x requires owning the full cycle; without full-SDLC and delegation experience, engineers excel mainly at the coding portion. Paired with an expert "head" (an Analyst/PM/PO hybrid), they unlock team-level output. The future default structure is the micro-team: 1 PM/Analyst/QA hybrid + 2 engineers replaces the old 1 PM + 1 Analyst + 5 SDE + 2 SDET nine-person team, at equal or higher output. This is the structural basis for RACE Programming's Pit Crew.

Worked example

Walk the arithmetic in the statement. For an engineer without full-SDLC delegation experience, AI speeds up coding by roughly 20x. But coding is only about 30% of end-to-end delivery; the rest is requirements, design, review, testing, and coordination. So the net acceleration is roughly 20x × 30% ≈ 3x, not 20x. Apply that to team size: three such engineers, paired with one expert head who owns the requirements-to-acceptance work, produce what a nine-person Scrum team used to. The old 1 PM + 1 Analyst + 5 SDE + 2 SDET collapses into a 1 hybrid + 2 engineers micro-team at equal or higher output.

Why it holds

Two well-known results explain why the shrink is real and not just faster typing. The first is Amazon's two-pizza rule: a team should be small enough to feed with two pizzas, because coordination cost climbs with headcount. The second, sharper, is Brooks's Law: adding people to a software effort adds communication overhead that grows roughly with the square of team size, which is why adding manpower to a late project can make it later.

AI attacks exactly the part Brooks's Law penalizes. It takes headcount off the critical path, so the coordination tax falls even as output holds. The two-pizza rule set a ceiling on how large a team should get; this theorem lowers the floor on how small an effective team can be. It is the structural basis for RACE Programming's Pit Crew: a deliberately tiny execution unit that a larger team's coordination overhead would only slow down.

FAQ

How does this relate to the two-pizza team rule?

The two-pizza team caps a team at what two pizzas feed, roughly six to nine people. This theorem says AI shrinks it further: a 3-person micro-team matches a 9-person Scrum team, so the effective team gets smaller, not just better fed.

Why 3x and not 20x?

Because coding is only about 30% of delivery. A 20x speedup on 30% of the work nets to roughly 3x overall. The 20x is real but bounded by the share of the job it touches.


← All theorems

FAQ

Frequently asked questions

How does this relate to the two-pizza team rule?
The two-pizza team caps a team at what two pizzas feed, roughly six to nine people. This theorem says AI shrinks it further: a 3-person micro-team matches a 9-person Scrum team, so the effective team gets smaller, not just better fed.
Why 3x and not 20x?
Because coding is only about 30% of delivery. A 20x speedup on 30% of the work nets to roughly 3x overall. The 20x is real but bounded by the share of the job it touches.