Scrum
Timeboxed sprints focused on a valuable goal and a usable increment.
Scrum organises work into fixed-length sprints, each focused on a single Sprint Goal. At the end of every sprint, the team produces a usable increment and reflects on how to improve. The cadence of planning, delivery, review, and retrospective gives teams a predictable rhythm and regular opportunities to change direction.
What it's for
Scrum works well for product teams that benefit from a regular planning and feedback cadence — teams that maintain a prioritised backlog of user-facing work, commit to goals in short cycles, and need stakeholders to review working software on a predictable schedule.
Work item types
| Type | Description |
|---|---|
| Epic | A larger product outcome that groups related stories |
| Story | A valuable user-facing slice of an epic |
| Bug | A defect to correct |
| Task | Supporting delivery work inside a story or epic |
| Spike | Timeboxed learning work to reduce uncertainty |
Epics sit at the top of the hierarchy. Stories, bugs, tasks, and spikes roll up into epics.
Workflow
The board uses five columns:
| Column | Meaning |
|---|---|
| Backlog | Items not yet selected for a sprint |
| Selected | Items the team has committed to for the current sprint |
| In Progress | Active work (WIP limit: 5) |
| In Review | Work awaiting feedback or test (WIP limit: 3) |
| Done | Work meeting the Definition of Done |
Items move from Backlog through Selected into active development once a sprint starts.
Rituals
Skopo calls these Scrum Events in the sidebar.
| Event | When | Purpose |
|---|---|---|
| Sprint Planning | Each sprint | Set a Sprint Goal and select the work |
| Daily Scrum | Daily | Inspect progress toward the Sprint Goal |
| Sprint Review | Each sprint | Inspect the increment with stakeholders |
| Sprint Retrospective | Each sprint | Improve team effectiveness and quality |
| Backlog Refinement | Ongoing | Clarify and decompose future work |
Each event is completed on Skopo's Rituals page, which persists structured outputs — decisions, selected work, action items — rather than just session notes.
Artifacts
- Product Goal — the long-term objective the product is working toward, tracked in the Product Goals view.
- Sprint Goal — the single commitment for the current sprint, set during Sprint Planning.
- Definition of Done — the shared quality checklist every item must meet before moving to Done.
Metrics
| Metric | What it measures |
|---|---|
| Sprint goal success | Whether the Sprint Goal was achieved at the end of the sprint |
| Burndown | Remaining sprint work over time, compared to an ideal burn line |
| Predictability | Completed work versus work selected at the start of the sprint |