Goal

Define the Scrum sprint frame for this project so that

  • Jira carries the operational sprint state,
  • GitHub Pages shows the public sprint history,
  • and the tagebuch remains the richer raw material for thinking and work flow.

Terms

  • Project backlog: all known, prioritised, or later possible work.
  • Sprint backlog: only the work that is actually pursued in the current sprint.
  • Active issue: not Done and part of the currently active sprint.

System roles

  • Jira: sprint state, sprint backlog, status flow, labels.
  • GitHub Pages: public sprint docs, sprint history, public Jira mirror.
  • tagebuch: raw material for thinking process, round protocols, observations, and the finer work flow.

Rules

  • All work that is actually handled in the sprint window belongs in the active sprint.
  • Sprint goal and sprint backlog are not identical.
  • Additional sprint work stays visible inside the sprint and gets a sprint category label.
  • If a sprint is already past its end date but still active in Jira: fix the sprint state first, then continue normal work.

Sprint categories

  • sprint-goal: direct work on the sprint goal.
  • sprint-support: work that secures, prepares, or unblocks goal work.
  • sprint-admin: docs, Jira, mirror, skill, or process work inside the sprint.
  • sprint-unplanned: work added during the sprint.

Public sprint artefacts

  • sprint planning
  • sprint review
  • sprint retro
  • carry-over
  • scope changes

These artefacts are published under work/sprints/.