Sizing
One definition of the T-shirt scale. Size on what the work looks like, never on how long it might take.
The scale
| Size |
Points |
What it looks like |
| XS |
1 |
Trivial and self-evident. A config change, a docs fix, a small bug fix, a single-file edit. No design decision. |
| S |
2 |
One focused slice, fully bounded. A standalone bug fix or feature slice with its own tests. Stays inside one module. |
| M |
3 |
The workhorse. Clear scope, one owner, several files in one subsystem, with tests and docs. |
| L |
5 |
The largest single unit. A new component, or a cross-cutting interface change with a settled design. |
| XL |
8 |
Personal projects only. Never on work: split into a parent plus children. |
Rules
- Index on what the work looks like, never on elapsed time. Do not estimate in days or weeks.
- Unresolved design is not a size, it is a spike. File the spike at XS or S, then size the real work once the design is settled.
- Parent tracking issues carry no estimate. The children carry the size.
- Work stops at L. Personal projects may use XL, but splitting is still the better move.
- Confirm the scale against the live workspace before assigning. The values above are what this workspace uses today, not a fixed truth.
Telling the workspaces apart
The WW team, Wimpy's World, is personal. The FUL team, Fulfillment Automation, is work.
Sprint loading
A human sanity check, not an agent input. A two-week sprint holds 8 XS, or 4 S, or 2 M, or 1 L.
1---2name: sizing3description: Sizing4---56# Sizing78One definition of the T-shirt scale. Size on what the work looks like, never on how long it might take.910## The scale1112| Size | Points | What it looks like |13| ---- | ------ | ------------------ |14| XS | 1 | Trivial and self-evident. A config change, a docs fix, a small bug fix, a single-file edit. No design decision. |15| S | 2 | One focused slice, fully bounded. A standalone bug fix or feature slice with its own tests. Stays inside one module. |16| M | 3 | The workhorse. Clear scope, one owner, several files in one subsystem, with tests and docs. |17| L | 5 | The largest single unit. A new component, or a cross-cutting interface change with a settled design. |18| XL | 8 | Personal projects only. Never on work: split into a parent plus children. |1920## Rules2122- Index on what the work looks like, never on elapsed time. Do not estimate in days or weeks.23- Unresolved design is not a size, it is a spike. File the spike at XS or S, then size the real work once the design is settled.24- Parent tracking issues carry no estimate. The children carry the size.25- Work stops at L. Personal projects may use XL, but splitting is still the better move.26- Confirm the scale against the live workspace before assigning. The values above are what this workspace uses today, not a fixed truth.2728## Telling the workspaces apart2930The `WW` team, Wimpy's World, is personal. The `FUL` team, Fulfillment Automation, is work.3132## Sprint loading3334A human sanity check, not an agent input. A two-week sprint holds 8 XS, or 4 S, or 2 M, or 1 L.
wimpysworld