Sprints, goals & retros
The delivery cycle: sprint CRUD, goal progress, retro notes and action items.
Sprints, goals & retros
Sprints
/dashboard/sprints is full CRUD over the sprints table (name, start date, end date, status). Tasks reference a sprint through sprintId, so a sprint view is a filter rather than a copy of the data.
- Create the sprint.
- Pull tasks in from /dashboard/backlog.
- Watch completion on /dashboard/ai-scrum-master (burndown, velocity forecast, health score).
- Close it and run a retro.
/api/sprints, /api/sprints/<id> and /api/sprints/<id>/tasks back the page. Sprint-level analytics are stored separately in sprint_analytics so historical charts stay stable after the sprint closes.
Goals
/dashboard/goals tracks longer-horizon objectives with owner, target date and progress. Progress is updated through /api/goals/<id>/progress, and the goals page renders the trend rather than a single percentage. Link a goal to a sprint when the sprint is the thing that moves it.
Retrospectives
/dashboard/retros gives each sprint a retro with three kinds of record:
- Notes: what went well, what did not, what to try. Created and deleted through /api/retros/<id>/notes and /api/retros/<id>/notes/<noteId>.
- Votes: members vote on notes so the loudest topic is the one you discuss. /api/retros/<id>/notes/<noteId>/vote.
- Action items: an owner and a state, carried into the next sprint. /api/retros/<id>/actions and /api/retros/<id>/actions/<actionId>.
The cycle in one picture
- Backlog grooming — estimate and prioritise.
- AI draft plan — accept, edit or dismiss each recommendation.
- Delivery — kanban during the sprint, health score and burndown alongside.
- Retro — notes, votes, action items.
- Goals — roll the outcomes up into the objective they serve.
Notifications
Starting a sprint, closing one, creating an action item and completing a goal each write a notification for the people affected, which the bell and the SSE feed deliver.