Open a new sprint

Table of Contents

This page documents a runbook — a named, repeatable composition of recipes and skills for a complete multi-step procedure. Each step references a recipe or skill by id-link.

Goal

Close the current sprint, generate release notes, scaffold a new sprint folder, and bump the project version — the full sprint-transition ceremony.

Preconditions

  • Current sprint's stories are DONE, ABANDONED, or about to be carried to the product backlog (PR 1 below).
  • You are on main with a clean working tree.
  • SSH_AUTH_SOCK is exported (see SSH memory).

Steps

The transition is two PRs: the first closes the old sprint, the second opens the new one. Never combine them.

PR 1 — close the current sprint

  1. Carry unfinished work to the product backlog. Follow the carry mechanics in Sprint closure: move unfinished stories by file into the inbox preserving their immutable IDs (flat story.org for undecomposed stories, whole folders when task history exists), mark their sprint-table rows ABANDONED, and re-run the backlog index regeneration.
  2. Generate release notes. Follow How do I generate release notes? for the closing sprint: scaffold via compass add release_notes, populate, and link from the sprint.
  3. Close the current sprint. Write Achievements and the Retrospective, mark the sprint DONE with its End date, update the version's sprint table, and raise the closing PR.

PR 2 — open the new sprint

  1. Scaffold the new sprint. Use How do I open a new sprint? to create the sprint folder, sprint.org, wire it into the version, and update the vcpkg submodule to latest. Pull carried stories back from the inbox by moving their files into the new sprint (IDs travel with them).
  2. Bump the project version. Follow How do I bump the project version? to update CMake version strings and tags. Land this as a separate commit on the same PR — do not open a third PR.
  3. Commit and PR. Use ORE Studio commit conventions and follow How do I create a PR? — title [COMPONENT] Description, body sections Summary / Changes / Traceability.

Postconditions

  • Old sprint is DONE with release notes.
  • New sprint exists and is STARTED.
  • Project version is bumped.
  • PR is open.

See also

Emacs 29.1 (Org mode 9.6.6)