Story: Sprint 01 housekeeping
Table of Contents
This page documents a story in Sprint 01. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
Goal
Catch the work that has to happen for the sprint itself to function but does not deliver a user-visible outcome: sprint backlog refinement, sprint resourcing reporting, story classification, dev machine setup, community channel.
This is the pattern story — every sprint will have one
sprint_NN_housekeeping equivalent. Treating sundries as a real
story keeps the composition invariant (task → story → sprint) intact.
Status
| Field | Value |
|---|---|
| State | DONE |
| Parent sprint | Sprint 01 |
| Now | Story closed; sprint backlog refined, resourcing chart in place, stories classified by tag, dev laptop set up, Discord channel created. |
| Waiting on | None. |
| Next | None. |
| Last touched | 2024-07-28 |
Acceptance
- Sprint backlog has been refined and tagged consistently.
- A resourcing-per-story chart is generated as part of the sprint report.
- Stories are classified by their dominant tag.
- The developer laptop is set up to build and run the project.
- A community channel (Discord) is created.
Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Use a bar chart for sprint resourcing cost | DONE | 2024-07-15 | 2024-07-21 | Produce a per-story resourcing bar chart from the sprint's clocktable for the sprint report. |
| Classify stories by type | DONE | 2024-07-22 | 2024-07-22 | Apply consistent tag classification to every story in the sprint and reflect the classification in the sprint report. |
| Setup laptop for development | DONE | 2024-07-09 | 2024-07-15 | Install all required toolchains, libraries, and editor configuration on the dev laptop. |
Decisions
- Housekeeping as a real story
- rather than allowing tasks to exist without a parent story, every sprint has one explicit housekeeping story. Keeps invariants strict; small cost in ceremony.
Out of scope
- Long-term agile tooling beyond what the sprint needs immediately.
- Cross-sprint instrumentation (would be its own story when needed).
See also
- Sprint 02 housekeeping / Sprint 03 housekeeping — successor housekeeping stories. Pattern: one per sprint.
- Compass — v2 retired the per-entry tag classification (its v0 tag-by-letter mechanism became the v2 multi-dimensional filetag system).