blob: 7321b44c9318fa4d81bb9b1ecf2f0f21d693aec0 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
|
# How to use Jira - Scrum template
[](#How%20to%20use%20Jira%20-%20Scrum%20template)
**Article Created: 24 July 2020** || **Last Edited: 16 September 2020**
[`<<`](./introduction.html) || [`< Kanban template`](./kanban.html) || [`Bug tracking template >`](./bug.html)
---
The scrum template is very similar to the kanban template, with one big difference: **sprints**.
**All issues** are put into the **backlog** (which is now a **separate page**). From there, they are organised into **sprints**.
In general [agile software development](https://www.atlassian.com/agile), a **sprint is a small duration of time** (one to four weeks) where the team focuses on a **set of tasks** and at the end everyone **evaluates the results** and plans the next sprint.
Your **boards only work on the issues of the currently active sprint**.
## Backlog
[](#Backlog)
As we've discussed, the **backlog** is used for organising **all issues** into **sprints**.

From here you can also organise **Versions** (refer to [Releases](./releases.html)) and **Epics** (refer to [Cards](./cards.html)). An important note is that Epics in this context don't need to have their linked issues in only one sprint.

Creating a sprint is done from the conveniently named `Create sprint` button. It shows a box on top where you can either move issues from the backlog to the sprint or create entirely new issues.

## Boards and Issues
[](#Boards%20and%20Issues)
As previously mentioned, boards have access only to the issues in the active sprint. This is also reflected in the user interface. After selecting a board from the sidebar, you view it from the `Active sprints` page.

## Create board
[](#Create%20board)
This template can be chosen when **creating a project**

and **from the `Create board` screen**.

|