The migration example highlights a different part of the process: rollback drafted. Write an exit criterion before setting a delivery date. Separate required work from attractive additions. Compare it with export csv before assuming that both items require the same response.
Work through the specimen
A backlog measures demand; it does not define a release. Unresolved dependencies are where schedules begin to drift.
Example: Migration
The illustrative record contains rollback drafted. Its state is review. Ask what evidence supports that state, which detail is still uncertain and whether the next person could understand it without reading a separate message thread.
Questions for a working review
- Check the current condition against the stated context. For migration, use “Rollback drafted” as the starting context.
- Identify which role can verify the information. For migration, use “Rollback drafted” as the starting context.
- Record the exception as well as the expected path. For migration, use “Rollback drafted” as the starting context.
A small exercise
Take one recent release planning example from your own process. Write its context without using a status label, then add the label separately. If the two contradict each other, investigate the source before updating the record. Compare the result with “Export CSV” in the demonstration to see which distinctions your process needs.
These are planning notes. The specimen is illustrative, and the preview does not process live work.
More field notes →