Overview
This page describes how Youtap use Jira and Confluence to manage scrum teams. See Jira for more generic details on how we use Jira.
Squads
There is a custom field on all Jira projects called Squad. The value of this field are the squad names, and also ‘No Squad’. When tickets are created, where it is known, the correct squad should be assigned.
This field is what determines which backlog the ticket goes in. Each team’s board has a filter that filters on the Squad value to include tickets on their board.
Tickets cannot be assigned to more than one Squad at a time.
Boards
Each Squad has one Sprint Board normally called ‘[Squad Name] Squad’
Columns
The boards are set up with 7 columns.
|
Column |
Matching Workflow States |
|---|---|
|
To Do |
In Design, To Do, QA Failed |
|
Development |
Development, Blocked |
|
Review |
To Review |
|
Merged |
Merged |
|
QA Ready |
QA Ready |
|
Testing |
Testing |
|
QA Passed / Done |
QA Passed, Closed |
Swimlanes, Quick Filters, Card Colours
These can be configured as each teams desire. It’s popular to be able to quickly see the ‘Highest’ priority tickets.
Card Layout
Backlog - Status
Active Sprints - Sum Time Spent
Estimation
Story Points
Working days
Should be set to the team’s standard working days and time zones.
Sprints
-
Sprints are two weeks long, and should normally run Tuesday - Tuesday.
-
Sprints are named [Squad Name] [yy.nn]. E.g. Delta 23.15 (followed by Delta 23.16). All teams should be on the same numbered sprint.
-
Only one sprint is active per Squad at a time.
-
Future sprints should be created in the backlog as needed, and the Backlog bucked used for items not assigned to sprints.