Sprint Management
Open sprint
- Confirm sprint number, theme, duration, and objectives.
- Ensure
mainis clean and up to date. - Create
sprint-XX-topicbranch. - Create
docs/sprints/sprint-XX-topic.mdfrom template. - Update project constitution/current sprint metadata.
- Commit kickoff.
During sprint
- Use feature branches for isolated work.
- Merge into sprint branch.
- Keep sprint doc updated with scope changes and delivered work.
- Use session logs for important decisions.
- Regenerate
CODEMAP.mdwhenever a code file is created, removed or renamed —node scripts/codemap.js. Doing it as you go beats doing it all at close.
Close sprint
- Confirm all intended work is merged or explicitly deferred.
- Run tests and quality gates.
- Invoke coordinator review.
- Invoke adversarial review for meaningful releases.
- Update changelog.
- Regenerate the codemap —
node scripts/codemap.js— and commit it if it changed. - Update sprint doc with final status and retrospective.
- Merge sprint branch into
main. - Tag release.