Deliveries

A delivery is one outcome with its plan, tasks, agents, evidence and your decisions. How it starts, what its page shows and how it ends.

A delivery is the unit of work in Blume: one outcome and everything needed to trust that it was reached. It is not a branch, a pull request or a conversation, and it can span several of each.

We recommend one delivery per outcome, small enough to review in one sitting. See Outcomes, not output and Small deliveries.

How a delivery starts

Agents create deliveries. The app has no button for it.

  1. You ask a connected agent to build, change, fix or test something.
  2. The agent compares your request with the project’s open deliveries.
  3. If one matches, it resumes it. If several could match, it asks you. If none matches, it creates a delivery named after the outcome, in the Start phase.

The Deliveries list

The list has four sections: NEEDS YOUR ATTENTION, ACTIVE, RECENT and ARCHIVED. When something waits on you, the page leads with These need your attention. See Questions and requests.

The Deliveries list: four deliveries under Needs your attention and five under Active, each row showing its phase, how long ago it moved, its title, workspace, pull request count and task progress.The Deliveries list: four deliveries under Needs your attention and five under Active, each row showing its phase, how long ago it moved, its title, workspace, pull request count and task progress.
The Deliveries list in Blume, with what needs you at the top and the active deliveries below.

The delivery page

ViewShows
OverviewWhat waits on you, then a summary box for each other view.
PhasesThe phase history, newest first.
TimelineEverything that happened.
PlanThe outcome, the plan’s facts and the spec.
PRsThe pull requests with their checks and reviews.
EvidenceThe test runs and reported evidence at the current revision.
RevisionsEvery revision sent for review.
ReleaseEach application’s release steps.

On the Overview, Waiting on you shows the review that is due. Choose Review to open it. Also waiting on you lists the agents’ open questions, which you answer in place.

A delivery's Overview: its phase, title and outcome, the tab row, the Work complete bar at 5 of 5, and a Waiting on you card for an outcome review with its evidence strip and the Review button.A delivery's Overview: its phase, title and outcome, the tab row, the Work complete bar at 5 of 5, and a Waiting on you card for an outcome review with its evidence strip and the Review button.
A delivery's Overview. The Waiting on you card holds the decision the delivery needs from you, with the evidence to decide it.

A failing check or a step taken without approval appears as a note, under Failing or Not approved. The phase is not held back. See Notes over blocks.

How a delivery ends

A delivery is Done when every application it changes is live and checked where its users are. One that ships no application is Done when its pull requests are merged.

  • To put a delivery away, open the … menu in its header and choose Archive. Nothing is deleted.
  • To correct a phase, click the phase badge and choose a phase under Move this delivery to.