diff options
Improved wording, format and errors in the rest of how to use jira tutorial pages
1 files changed, 12 insertions, 15 deletions
| -rw-r--r-- | src/tutorials/how-to-use-jira/scrum.md | 27 |
diff --git a/src/tutorials/how-to-use-jira/scrum.md b/src/tutorials/how-to-use-jira/scrum.md index 948466a..2a5a10e 100644 --- a/src/tutorials/how-to-use-jira/scrum.md +++ b/src/tutorials/how-to-use-jira/scrum.md @@ -1,22 +1,26 @@ # How to use Jira - Scrum template -**Article Created: 24 July 2020** || **Last Edited: 10 September 2020** +**Article Created: 24 July 2020** || **Last Edited: 16 September 2020** [`<<`](./introduction.html) || [`< Kanban template`](./kanban.html) || [`Bug tracking template >`](./bug.html) --- -**Scrum is a [framework](https://stackoverflow.com/a/12733126/12036073) for [agile software development](https://www.atlassian.com/agile) where teams develop software in intervals, called sprints**. +The scrum template is very similar to the kanban template, with one big difference: **sprints**. -During a sprint, a **Scrum Master** organises and makes sure everyone follows the methodology. A Daily Scrum is held each day where **everyone shares what they have done the previous day and what they will do to the current day**. A retrospective happens at **the end of each sprint, where the team evaluates results and plans the next sprint**. +**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 -Contrary to the [Kanban template](./kanban.html), the backlog has a very important role. **The backlog is used to plan issues for any future sprints (see Boards and Issues below)**. +As we've discussed, the **backlog** is used for organising **all issues** into **sprints**.  -From here you can also organise **Versions** (explained in more detail in [Releases](./releases.html)) and **Epics** (explained in more detail in [Cards](./cards.html)). An important note is that Epics in this context don't need to have their linked issues fixed in one sprint. +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.  @@ -26,24 +30,17 @@ Creating a sprint is done from the conveniently named `Create sprint` button. It ## Boards and Issues -Boards and issues (cards) **work mostly the same as explained in the [Project](./project.html) page**. - -However there is one big difference, **issues are put into the backlog**. So, **boards are used to organise a sprint's issues**, not all issues. - -This is also reflected in the user interface. After selecting a board from the sidebar, you view it from the `Active sprints` page. +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 -**This template can be either chosen when creating a project**, +This template can be chosen when **creating a project**  -or **from the `Create board` screen**. +and **from the `Create board` screen**.  -At it's core, the **scrum template controls how board, issues and cards work together**. **Each template is tied to it's given board**. - -**Note**: when you create a project, you can choose this template. This just means that the project will automatically create a new board with the template. |