Document type: sprint

Table of Contents

This page defines the sprint document type — one entry in the document types taxonomy. The general contract every document follows (frontmatter, state, linking, tags) lives on the taxonomy page; this page carries only what is specific to sprint.

Contract

Folder
versions/<v>/<sprint_NN>/sprint.org
Title
Sprint NN — no prefix (the word "Sprint" is already in the title).
Level
s3
TODO vocabulary
STARTED | DONE (sprints don't go through BACKLOG; they exist when they exist, and lexicographic order tells you which is current).
How to create
see New sprint in the codegen recipe.
Required sections (in this order)
  • Blurb — opens with This page documents a [[id:0820B7FD-147C-4832-AC25-C043D38D5B61][sprint]] (*Sprint NN*) of ORE Studio. ... see [[id:<parent_version_id>][<parent_version_title>]].
  • * Mission — one or two paragraphs / bullets: what this sprint exists to achieve.
  • * Status — table; rows State / Parent version / Start / End (expected) / Now / Waiting on / Next / Last touched.
  • * Stories — table with class hug-leading; columns Story / State / Start / End / Theme. Story column carries the id-link to each child story.
  • * Achievements — milestones worth capturing as they happen (e.g. "all builds green", a demo, a headline number), each with a dated ** subheading and any evidence (screenshot via [[proj:assets/images/<file>.png]]). It is the standing evidence drawer the release notes draw from at close — append to it through the sprint rather than reconstructing milestones at the end.
  • * Retrospective — filled at close.

A sprint folder may also contain an inbox/ subfolder for untriaged discovered tasks that didn't fit any existing story at the time of discovery (see lifecycle).

Emacs 29.1 (Org mode 9.6.6)