Commit Backlogs

pull/7998/head
birthe 5 years ago
parent a244906031
commit d37be23b03
  1. 24
      help/user-guide/backlogs-scrum/README.md
  2. 32
      help/user-guide/backlogs-scrum/manage-sprints/README.md
  3. BIN
      help/user-guide/backlogs-scrum/manage-sprints/User-guide-backlogs-manage-sprints.png
  4. BIN
      help/user-guide/backlogs-scrum/manage-sprints/User-guide-backlogs-manage-versions.png
  5. 29
      help/user-guide/backlogs-scrum/print-story-cards/README.md
  6. 29
      help/user-guide/backlogs-scrum/sprint-wiki/README.md
  7. 51
      help/user-guide/backlogs-scrum/taskboard/README.md
  8. BIN
      help/user-guide/backlogs-scrum/taskboard/User-guide-new-task.png
  9. BIN
      help/user-guide/backlogs-scrum/taskboard/User-guide-sprint-impediments.png
  10. BIN
      help/user-guide/backlogs-scrum/taskboard/User-guide-task-color.png
  11. BIN
      help/user-guide/backlogs-scrum/taskboard/User-guide-taskboard.png
  12. BIN
      help/user-guide/backlogs-scrum/taskboard/image-20200129132035246.png
  13. BIN
      help/user-guide/backlogs-scrum/taskboard/image-20200129132413044.png
  14. 140
      help/user-guide/backlogs-scrum/work-with-backlogs/README.md
  15. BIN
      help/user-guide/backlogs-scrum/work-with-backlogs/User-guide-backlogs-burndown-chart.png
  16. BIN
      help/user-guide/backlogs-scrum/work-with-backlogs/User-guide-backlogs-edit-story-points.png
  17. BIN
      help/user-guide/backlogs-scrum/work-with-backlogs/User-guide-backlogs-estimate-story-points.png
  18. BIN
      help/user-guide/backlogs-scrum/work-with-backlogs/User-guide-backlogs-new-story.png
  19. BIN
      help/user-guide/backlogs-scrum/work-with-backlogs/User-guide-backlogs-prioritize-user-stories.png
  20. BIN
      help/user-guide/backlogs-scrum/work-with-backlogs/User-guide-backlogs-sprint-duration.png
  21. BIN
      help/user-guide/backlogs-scrum/work-with-backlogs/User-guide-backlogs-stories.png
  22. BIN
      help/user-guide/backlogs-scrum/work-with-backlogs/User-guide-create-story-backlogs.png
  23. BIN
      help/user-guide/backlogs-scrum/work-with-backlogs/User-guide-print-story-cards.png
  24. BIN
      help/user-guide/backlogs-scrum/work-with-backlogs/User-guide-sprint-wiki.png
  25. BIN
      help/user-guide/backlogs-scrum/work-with-backlogs/image-20200127164402798.png
  26. BIN
      help/user-guide/backlogs-scrum/work-with-backlogs/image-20200129140655485.png
  27. 2
      help/user-guide/project-settings/versions/README.md
  28. 11
      help/user-guide/project-settings/versions/versions-backlogs/README.md

@ -9,13 +9,21 @@ keywords: backlogs, scrum
# Backlogs (Scrum)
XX
Working in agile project teams is becoming increasingly important.
| Feature | Documentation for |
| ------------------------------------------------------------ | ----------------- |
| TODO | |
| | |
| | |
| | |
| | |
OpenProject supports your work with the Scrum methodology by providing a variety of functionalities. You can record and prioritize user stories in the sprint and product backlog, use digital task boards or burndown-charts, print story cards, and much more. For more information, please refer to the OpenProject [agile and scrum features](https://www.openproject.org/collaboration-software-features/agile-scrum-agile-project-management-openproject/) page.
Please note that this user guide does not represent an introduction into scrum methodology, but merely explains the scrum-related functionalities and user instructions in OpenProject.
| Feature | Documentation for |
| ------------------------------------------------------------ | ------------------------------------------------------------ |
| [Working with backlogs](work-with-backlogs) | How to work with backlogs for Scrum projects in OpenProject? |
| [Create new sprint](manage-sprints) | How to set up the product backlog, bug backlog, and create a new sprint in the backlogs view? |
| [Story points](story-points) | How to estimate and edit story points in the backlogs view? |
| [Create a new user story](create-new-story) | How to create a new epic, user story, bug or feature in the backlogs view? |
| [Task board](taskboard) | How to work with the taskboard? |
| [Burndown chart](burndown-chart) | |
| [Print story cards](https://www.openproject.org/help/agile-scrum/print-story-cards/) | |
| [Sprint wiki page](https://www.openproject.org/help/agile-scrum/create-sprint-wiki-page/) | |
| [Selecting folded or collapsed backlogs view](https://www.openproject.org/help/agile-scrum/selecting-folded-collapsed-backlogs-view/) | |

@ -0,0 +1,32 @@
---
sidebar_navigation:
title: Manage sprints
priority: 900
description: Create a new sprint in the backlogs view.
robots: index, follow
keywords: manage sprints
---
# Create a new sprint
Sprints are technically a version in OpenProject. Therefore, creating a sprint is done following the same procedure as for creating a new version.
It is advisable to number your sprints chronologically for a better overview. Sprints usually run for a fixed period of approx. two to three weeks. In order to configure these settings, click on the Sprint title in the backlogs view.
For some settings, such as start and end date, you can also use in-line editing.
Click on the arrow next to a sprint and select -> *Properties*.
![User-guide-backlogs-manage-sprints](User-guide-backlogs-manage-sprints.png)
On the new page, you can specify details of the version such as description, status, (sprint) wiki page, start and end date, as well as sharing options across projects. Moreover, you can create a custom field and decide where the version is to be displayed in the backlog.
The Column in backlog settings define whether the version should be displayed in the backlogs view on the left side (recommended for sprints) or on the right side (recommended for product backlog, bug backlog, wishlist, etc.)
<div class="alert alert-info" role="alert">
**Note**: Sprints (versions displayed on the left side of the backlogs page) offer more options – such as opening the task board and displaying the burndown chart.
</div>
![User-guide-backlogs-manage-versions](User-guide-backlogs-manage-versions.png)

Binary file not shown.

After

Width:  |  Height:  |  Size: 132 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 101 KiB

@ -0,0 +1,29 @@
---
sidebar_navigation:
title: Backlogs (Scrum)
priority: 850
description: Support your Scrum methodology with Backlogs
robots: index, follow
keywords: backlogs, scrum
---
# Backlogs (Scrum)
Working in agile project teams is becoming increasingly important.
OpenProject supports your work with the Scrum methodology by providing a variety of functionalities. You can record and prioritize user stories in the sprint and product backlog, use digital task boards or burndown-charts, print story cards, and much more. For more information, please refer to the OpenProject [agile and scrum features](https://www.openproject.org/collaboration-software-features/agile-scrum-agile-project-management-openproject/) page.
Please note that this user guide does not represent an introduction into scrum methodology, but merely explains the scrum-related functionalities and user instructions in OpenProject.
| Feature | Documentation for |
| ------------------------------------------------------------ | ----------------- |
| [Working with backlogs](https://www.openproject.org/help/agile-scrum/working-backlogs/) | |
| [Create new sprint](https://www.openproject.org/help/agile-scrum/create-new-sprint/) | |
| [Edit story points in backlog view](https://www.openproject.org/help/agile-scrum/edit-story-points-backlog-view/) | |
| [Create new epic, user story, bug or feature in backlog view](https://www.openproject.org/help/agile-scrum/create-new-epic-user-story-bug-feature-backlog-view/) | |
| [Working with the task board](https://www.openproject.org/help/agile-scrum/working-task-board/) | |
| [Burndown chart](https://www.openproject.org/help/agile-scrum/burndown-chart/) | |
| [Print story cards](https://www.openproject.org/help/agile-scrum/print-story-cards/) | |
| [Create a sprint wiki page](https://www.openproject.org/help/agile-scrum/create-sprint-wiki-page/) | |
| [Selecting folded or collapsed backlogs view](https://www.openproject.org/help/agile-scrum/selecting-folded-collapsed-backlogs-view/) | |

@ -0,0 +1,29 @@
---
sidebar_navigation:
title: Backlogs (Scrum)
priority: 850
description: Support your Scrum methodology with Backlogs
robots: index, follow
keywords: backlogs, scrum
---
# Backlogs (Scrum)
Working in agile project teams is becoming increasingly important.
OpenProject supports your work with the Scrum methodology by providing a variety of functionalities. You can record and prioritize user stories in the sprint and product backlog, use digital task boards or burndown-charts, print story cards, and much more. For more information, please refer to the OpenProject [agile and scrum features](https://www.openproject.org/collaboration-software-features/agile-scrum-agile-project-management-openproject/) page.
Please note that this user guide does not represent an introduction into scrum methodology, but merely explains the scrum-related functionalities and user instructions in OpenProject.
| Feature | Documentation for |
| ------------------------------------------------------------ | ----------------- |
| [Working with backlogs](https://www.openproject.org/help/agile-scrum/working-backlogs/) | |
| [Create new sprint](https://www.openproject.org/help/agile-scrum/create-new-sprint/) | |
| [Edit story points in backlog view](https://www.openproject.org/help/agile-scrum/edit-story-points-backlog-view/) | |
| [Create new epic, user story, bug or feature in backlog view](https://www.openproject.org/help/agile-scrum/create-new-epic-user-story-bug-feature-backlog-view/) | |
| [Working with the task board](https://www.openproject.org/help/agile-scrum/working-task-board/) | |
| [Burndown chart](https://www.openproject.org/help/agile-scrum/burndown-chart/) | |
| [Print story cards](https://www.openproject.org/help/agile-scrum/print-story-cards/) | |
| [Create a sprint wiki page](https://www.openproject.org/help/agile-scrum/create-sprint-wiki-page/) | |
| [Selecting folded or collapsed backlogs view](https://www.openproject.org/help/agile-scrum/selecting-folded-collapsed-backlogs-view/) | |

@ -0,0 +1,51 @@
---
sidebar_navigation:
title: Taskboard
priority: 850
description: Taskboard in OpenProject.
robots: index, follow
keywords: taskboard
---
# Working with the Task Board
To support daily scrum meetings, all of a team’s tasks and sprint impediments are recorded in a digital task board. The digital task board thus allows team members to get a fast overview of the current state of a sprint.
To open the task board view, click on the small arrow next to the respective sprint, and select *Task board* in the drop-down menu.
![User-guide-taskboard](User-guide-taskboard.png)
You will find user stories in the left column, followed by their individual tasks (as child work packages) which are sorted by status. Therefore, you can immediately see the status of a user story and its associated tasks. Clicking on the *+*-icon next to a user story opens a window to create a new task.
![User-guide-new-task](User-guide-new-task.png)
Here, you can set the fields *Subject*, *Assigned To*, and *Remaining Hours*. The new task will be created as a child element of the user story in the same row.
If a task is updated or completed, it can be moved to the respective column by a team member using drag&drop.
In the background, the status of the work package will be adjusted accordingly. Clicking on the work package number opens the work package’s detail view.
![drag and drop taskboard](image-20200129132035246.png)
On the very top of the table, sprint impediments are documented and assigned to the scrum master for removal.
![User-guide-sprint-impediments](User-guide-sprint-impediments.png)
<div class="alert alert-info" role="alert">
**Note**: If you add an impediment and type the work package number into the field Blocked (ID), the respective work package will be linked to the impediment. As long as the impediment remains, the work package cannot be closed.
</div>
![sprint impediments](image-20200129132413044.png)
The task colors are different for every team member, making it easy to associate tasks with their respective assignees.
## Configure Backlogs settings under My Account
If needed, the coloring can be adjusted in the personal user account settings (-> *My Account*). Use hex codes to specify the desired color.
![User-guide-task-color](User-guide-task-color.png)
Here, you can also specify whether the versions in the Backlogs view should be displayed folded. You can choose whether backlogs are to be displayed folded or collapsed by default. In *My account*, select *Settings* from the side menu and check or uncheck the respective box next to the field *Show versions folded*.

Binary file not shown.

After

Width:  |  Height:  |  Size: 157 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 230 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 112 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 225 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 92 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 78 KiB

@ -0,0 +1,140 @@
---
sidebar_navigation:
title: Working with backlogs
priority: 990
description: Working with backlogs (scrum)
robots: index, follow
keywords: backlogs, scrum
---
# Working with Backlogs
The starting point for effective work in Scrum teams is a well-maintained and prioritized product backlog as well as the creation of sprint backlogs. In OpenProject, you can easily record and specify requirements represented by user stories. Moreover, you can respond to inquiries and sort them by priority for implementation.
Moreover, please note that the backlogs module is not available in the accessibility mode, since it uses drag&drop functionalities which are not accessible. If you use the accessibility mode you can however perform the same actions (like viewing and editing work packages such as user stories and epics) from the work package list view.
| Feature | Documentation for |
| --------------------------------------------------- | ------------------------------------------------------------ |
| [Create a new backlog](#create-a-new-backlog) | How to create a new product backlog or sprint? |
| [Create a new user story](#create-a-new-user-story) | How to create a new user story, epic, bug in the backlogs view? |
| [Prioritize user stories](#prioritize-user-stories) | How to prioritize user stories in the backlogs view? |
| [Story points](#working-with-story-points) | Estimate user stories and document story points. |
| [Sprint duration](#editing-sprint-duration) | How to edit sprint duration? |
| [Burndown chart](#burndown-chart) | How to view the burndown chart? |
| [Print story cards](#print-story-cards) | How to print story cards for a physical task board? |
| [Sprint wiki](#sprint-wiki) | How to create a sprint wiki to document sprint information? |
## Create a new backlog
The first thing you will do is to **create a new backlog version** (product backlog or sprints). Read here on [creating a new backlogs version or a sprint](../../project-settings/versions/versions-backlogs). You can always manage the backlog versions under project settings, if you have the necessary administrator rights.
The versions (product backlog or sprint) will then appear in the module Backlogs either on the left or on the right side.
The Sprint 1, Sprint 2, Bug Backlog, Product Backlog in the example below are all versions in a project, displayed in the Backlogs view. You can create a new version with the green + Version button at the top of the backlogs view.
![backlogs view](image-20200127164402798.png)
## Create a new user story
In order to create a new work package in the product backlog, click on the arrow on the left of the product backlog and choose *New Story* from the drop-down menu.
![User-guide-backlogs-new-story](User-guide-backlogs-new-story.png)
Here, you directly specify the work package type, title, status and story points. The list contains those work package types that are activated in the System -> *Administration* -> *Backlogs*.
A new line will be added in the backlogs to enter work package information.
![User-guide-create-story-backlogs](User-guide-create-story-backlogs.png)
Clicking on the work package ID opens the work package full screen in a separate tab, where you can specify additional work package attributes.
Of course, new user stories can also be directly created following the usual procedure of [creating a new work package](../../work-packages/create-work-package/). In order to do so, choose a work package type and target version which are activated in the [backlogs settings in the Administration](../../../system-admin-guide/backlogs) – such as feature or bug, and product or sprint backlog, respectively.
**Displaying of all user stories and tasks for a sprint** is also possible by selecting *Stories/Tasks* in the drop-down menu next to the sprint title.
![User-guide-backlogs-stories](User-guide-backlogs-stories.png)
This will take you to the filtered work package view of all user stories and tasks in a sprint.
<div class="alert alert-info" role="alert">
**Note**: All tasks created for a user story via the task board view are automatically configured as child work packages of a user story. The task is thus always automatically assigned to the target version of the parent work package (i.e. the user story).
</div>
## Prioritize user stories
You can prioritize different work packages within the product backlog using drag & drop and you can assign them to a specific sprint backlog or re-order them within a sprint.
<div class="alert alert-info" role="alert">
**Note**: If you move a work package into the backlogs view, the target version will automatically be adapted in the background.
</div>
![User-guide-backlogs-prioritize-user-stories](User-guide-backlogs-prioritize-user-stories.png)
## Working with story points
In a sprint, you can directly document necessary effort as story points. The overall effort for a sprint is automatically calculated, whereby the sum of story points is displayed in the top row.
![User-guide-backlogs-estimate-story-points](User-guide-backlogs-estimate-story-points.png)
You can easily edit story points directly from the backlogs view. In order to do so, simply click in the line of the work package you want to edit, and make the desired changes.
In the same way, you can also edit the name, start and end date and status of a work package. To confirm your changes, press “*Enter*” on your keyboard. To cancel your changes, press “*Escape*”.
![User-guide-backlogs-edit-story-points](User-guide-backlogs-edit-story-points.png)
## Editing sprint duration
Moreover, you can adjust the start and end date of a backlog in the backlogs view. Clicking on the date opens a calendar where you can make your changes.
<div class="alert alert-info" role="alert">
**Note**: Apart from start and end date, you can also adjust the sprint name. To do so, you have to be a project administrator.
</div>
![User-guide-backlogs-sprint-duration](User-guide-backlogs-sprint-duration.png)
<div class="alert alert-info" role="alert">
**Note**: a backlog version will be shown under [Roadmap](../../roadmap/), but not in a [Gantt chart](../../gantt-chart). If you want to display a sprint in a timeline, you can create a new work package, select a phase as a work package type, give it the same name as to a specific version (for example Sprint 1) and assign the same start and end date.
</div>
## Burndown chart
**Burndown charts** are a helpful tool to visualize a sprint’s progress. With OpenProject, you can generate sprint and task burndown charts automatically. As a precondition, the sprint’s start and end date must be entered in the title and the information on story points is well maintained.
![User-guide-backlogs-burndown-chart](User-guide-backlogs-burndown-chart.png)
The sprint burndown is calculated from the sum of estimated story points. If a user story is set to “closed“ (or another status which is defined as closed (see admin settings)), it counts for the burndown.
The task burndown is calculated from the estimated number of hours necessary to complete a task. If a task is set to “closed“, the burndown is adjusted.
The remaining story points per sprint are displayed in the chart. Optionally, the ideal burndown can be displayed for reference. The ideal burndown assumes a linear completion of story points from the beginning to the end of a sprint.
![Burndown chart graph](https://1t1rycb9er64f1pgy2iuseow-wpengine.netdna-ssl.com/wp-content/uploads/2014/10/17_BurndownChart2.png)
## Print story cards
If you do not want to do without the real project pin board in your project management, OpenProject offers the option to print the user stories and tasks.
In order to so, select the *Export* option from the sprint drop-down menu in the backlogs view.
![User-guide-print-story-cards](User-guide-print-story-cards.png)
Choose a story card format from the list that will open. The format selection can only be adjusted by a system admin in the -> *Administration* -> *Backlogs* and applies to all projects in OpenProject.
Now, a PDF file is created which displays one or several stories or tasks per page (listing the work packages of the selected sprint), depending on the selected settings.
## Sprint wiki
OpenProject also allows you to create a wiki page associated with a sprint directly from the backlog. You can document sprint information, e.g. ratios, sprint meetings, retrospecitve, sprint planning or sprint review meetings.
In order to do so, click on the arrow on the left of the respective Sprint title to open the drop-down menu. A click on *Wiki* will take you to the Wiki editing page.
![User-guide-sprint-wiki](User-guide-sprint-wiki.png)
Here, you have all the tools for creating wiki pages at your disposal, with the title already pre-set and related to the selected sprint. You can insert and edit content using the text field and make changes to the formatting using the navigation pane above. You can also add comments and files from your hard drive. Once you have configured the wiki page according to your preferences, click *Save.*
![sprint wiki](image-20200129140655485.png)
<div class="alert alert-info" role="alert">
**Note**: You can configure the sprint wiki template in the -> Administration -> Backlogs. If you create a wiki page with the respective name, e.g. sprintwiki, all sprint wikis will use this wiki page as a template.
</div>

Binary file not shown.

After

Width:  |  Height:  |  Size: 214 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 215 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 180 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 172 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 196 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 288 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 222 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 224 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 164 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 230 KiB

@ -12,6 +12,8 @@ Versions will be used, e.g. for roadmap planning to track certain product versio
Also, version will be used to enable the Backlogs module, i.e. to create a product backlog and sprints in OpenProject.
[Read here how to create a new backlogs version](../../backlogs/manage-sprints).
## Create a new version
Press the green **+ Version** button to create a new version for a project.

@ -1,11 +0,0 @@
---
sidebar_navigation:
title: Versions for Backlogs (Scrum)
priority: 600
description: Manage versions for Backlogs in OpenProject.
robots: index, follow
keywords: manage versions backlogs
---
# Manage versions for Backlogs (Scrum)
Coming soon!
Loading…
Cancel
Save