Versions & team alignment
Finishing phases and stories, working in versions and drafts, and aligning the team.
Finish a phase
How to finish Discovery, Exploration or Planning: commit the phase’s version with a comment, clear what holds it back, and move on to the next phase.
Finish a story
How to commit a story’s version in Refinement, what holds it back, and how to change it later.
Versions and drafts
How a finished phase or story changes through a draft of its next version: starting and discarding drafts, deciding what a change affects, markers for review, and older versions.
What changed and what it may affect
For anyone finishing a draft of version 2 or later. How to read the change plan, decide which later elements need a review, and commit, including what to do when the assessment fails.
Resolve items marked for review
Where markers for review come from, where you see them, and how to resolve them as not relevant, postponed or handled so the phase or story can be finished. Also how to mark a story by hand.
When an earlier phase changes
What the "Based on older versions" pill means, and how to confirm that a finished phase or story still holds for a newer version of an earlier phase, or start its next version instead.
Team alignment
For project teams on the Professional and Business plans. How members vote "Ready" or "Not yet" before a phase or story is finished, how to ask for votes, and how to finish without everyone.
