Keep the plan true
The delivery's tasks list everything still needed for the outcome to be live, and they are kept current as the work changes.
At Blume, we ask one thing of a task list: at any moment, the open tasks are exactly what stands between now and the outcome being live. All of it, not only the coding part.
What goes wrong without it
Code tasks only
An agent plans a checkout change as five code tasks. It finds that the address table needs a migration, does it, and does not write it down. It ticks all five at the end and says the work is finished.
“Five of five” does not say that a migration was added, the end-to-end check has not run, the pull request is not merged and nothing is deployed.
The whole way
The same list, kept true:
- Build: Address selection in checkout. Address table migration, added when it was found.
- Test: Selection persists after a reload.
- Review: You review the result. The pull request is merged.
- Release: Deployed to production, and a production checkout is checked.
What to do
- List the whole way to live: tests, reviews, the merge, each release step and the check where the users are.
- Add work when you find it, before doing it.
- Mark tasks as they happen, never in one batch at the end.
- Remove with a reason.
- Do not tick the person’s tasks. A review is done when the person has reviewed.
In Blume
- Each delivery has one plan, a Markdown file in your repository. Blume reads its tasks on every save, and each save is a version.
- Tasks sit under their phase. Review tasks are completed by your approval.
- Changing an approved plan beyond progress marks needs a new approval where the project reviews plans. See plan review and release.