Scrum in ProjectBrain
Run fixed-length sprints with a clear backlog, a daily check-in and a review at the end.
Starter pack
Everything below, set up in one step. You can change any of it after.
Sprint timeline
Statuses
BacklogReadyIn progressIn reviewDoneBlueprints
- Sprint kickoff
- Definition of done check
- Release to production
Wiki and doc templates
- Sprint retro page
- Sprint goal brief
- Release notes
How a sprint flows
Section titled “How a sprint flows”Show the flow as text
- Backlog: Board, Backlog column.
- Sprint planning: Milestone page.
- Daily standup: Standups, Team view.
- Sprint review: Milestone, filtered to Done.
- Retro: Project Retro tab.
- Next sprint starts from the backlog.
When to use it
Section titled “When to use it”Pick Scrum when one team ships in small steps and priorities change between sprints. If work arrives all day without warning, Kanban fits better.
Recommended setup
Section titled “Recommended setup”| Area | Set it to |
|---|---|
| Statuses | BacklogReadyIn progressIn reviewDone |
| Task types | StoryBugSpikeChore |
| Labels | sprint-goalcarry-overtech-debt |
| Milestones | One per sprint, named “Sprint 14”. |
The product owner owns the backlog order. The scrum master runs the standup and clears blockers, so make them its facilitator. Developers pick up stories. Read the project manager guide if you wear the scrum master hat.
Typical roles: OwnerTeam leadIC
Metrics worth watching
Section titled “Metrics worth watching”- Velocity over the last five sprints.
- Carry-over: stories that rolled into the next sprint.
- Blocker age in working days.