Scrum Software Team
Two-week sprints for a product engineering team: stories, bugs and spikes move from backlog through code review and QA to done.
What's inside
What a new project starts with
Scrum Software Team.json23 KB
Workflow7 states
- Backlog
- Ready for Sprint
- In Progressmax 6
- Code Reviewmax 4
- QA
- Done
- Won't Do
Issue types5
StorydefaultBugTaskSpikeTech DebtLabels8
AreaFrontendBackendMobileInfrastructureDesignFlagsBlockedCustomer RequestNeeds Design
Custom fields4
- Acceptance Criteriamarkdown · Story · in the body
- Severityselect · Critical · Major · Minor · Trivial · Bug
- Reviewermember
- Pull Requesturl
Issue templates4
- User StoryStory · Backlog
- Bug ReportBug · Backlog
- SpikeSpike · Backlog
- Tech DebtTech Debt · Backlog · Low
Views13
- Sprint Boardboard
- Backlog Groomingtable
- Open Bugstable
- Code Reviewtable
- Blockedboard
- Roadmaptimeline
- Deadlinescalendar
- Sprint Healthdashboard
- Send to code reviewaction
- Send to QAaction
- Ship itaction
- Send back to developmentaction
- Escalate bugaction
Setup
- Cycles, on
- Initiatives, on
- Dashboards, on
- Docs, on
- Notes, on
- Subtasks, on
- Checklists, on
- Issue stats, on
- Time logging, off
- Estimates in story points
- Completed issues archive after 30 days
- Canceled issues archive after 7 days
- Open subtasks close with their parent
Quick start
Skip the setup, start the work
- 01
Import it in Project templates.
- 02
Open it to the teams that need it.
- 03
Pick it when you create a project.
A new project from this template · ready for issues