Phases

Start, Plan, Build, Test, Review, Release and Done. What each phase is for, what ends it, and why the phase follows where the work really is.

A delivery’s phase says where its work is right now. You see it as the badge in the delivery’s header, in the Deliveries list, and as history on the Phases tab.

  1. StartAgree on the outcome
  2. PlanSpec, tasks, acceptance checks
  3. BuildImplement the plan
  4. TestRun the checks, record evidence
  5. ReviewOutcome, then merge
  6. ReleaseEach application goes live
  7. DoneLive and verified
Build and Test repeat until the checks pass. Review and Release are where a person decides.
PhaseEnds when
StartThe outcome is agreed.
PlanThe plan is set.
BuildThe work is built.
TestThe delivery’s checks pass.
Review · Outcome reviewThe result is accepted.
Review · Merge reviewEvery pull request is merged.
ReleaseEvery application is live.
DoneThe delivery is complete.

The phase is a statement of fact, not a gate. Blume does not refuse a move because an earlier step was skipped. It moves the phase and records what was skipped on that visit. See Phases follow reality.

The Phases tab of a delivery in Test: the current visit open at the top with Now, Waits on and Next, and a test report with 1 of 3 checks failed; below it the earlier Build, Plan and Start visits.The Phases tab of a delivery in Test: the current visit open at the top with Now, Waits on and Next, and a test report with 1 of 3 checks failed; below it the earlier Build, Plan and Start visits.
The Phases tab of a delivery in Blume: the current visit and what it waits on, with the earlier visits below.

Going back

  • A failed check that needs a product fix sends the delivery back to Build, then to Test again.
  • Requesting changes in the outcome review returns the work to Build. The next round is a new revision.
  • A plan change becomes a new plan version. The delivery stays in its phase.

How the phase moves

  • The agent sets the phase at each milestone and after every commit or push.
  • Blume moves a delivery forward when it observes the facts. With GitHub connected, merged pull requests move it to Release, and applications that carry the merged code move it to Done.
  • You can set any phase: click the phase badge and choose one under Move this delivery to.

When Blume sees a fact that suggests the delivery has moved on, a Blume noticed bar appears. Choose Move to followed by the phase, or Not now.

Nothing moves a phase back on its own. A failing check after the merge shows as a note under Failing, and a missing approval as Not approved.

Read more: Outcome review, Merge review, Release