Keep deliveries small

Scope a delivery to one outcome that a person can review in one sitting. Agents make large changes cheap to produce, not cheap to review.

At Blume, we scope a delivery to one outcome, sized so that a person can review it in one sitting. The size of a change should be set by the reviewer’s attention, not by the agent’s speed.

What goes wrong without it

One big delivery

You ask an agent to “build team billing”. It arrives as one piece: twenty-three acceptance checks, forty tasks and a pull request with 6,000 changed lines.

The proration rule is wrong, so nothing ships, including the plans page that was ready hours ago. After the fix, all twenty-three checks must pass again.

Four small ones

The same feature as four deliveries:

  1. A team sees the available plans and its current one.
  2. Seats are counted and shown as members join and leave.
  3. A seat added mid-month is charged for the days left.
  4. The team’s owner receives an invoice email each month.

The plans page is released on the first day. The proration problem is found in delivery three, and its fix reruns five checks.

What to do

  • One outcome. If the sentence needs “and” to join two things a user could get separately, it is two deliveries.
  • Reviewable in one sitting. If the list of checks makes you want to skim, split.
  • Split along what users get, not along layers. “Backend for billing” cannot be reviewed as an outcome.
  • When a delivery grows, split off the new part if it is a separate outcome, or add the work to the plan. Do not let it grow silently.

In Blume