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.
Please note that the backlogs plugin must be installed and the backlogs module in the project configuration must be activated by the project administrator in order to be able to use scrum functionalities in OpenProject.
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.
Creating a new backlog
The first thing you will want to do is create a new backlog version. Read here on creating a new backlog version or a sprint. You can always manage the backlog versions under project settings, if you have the necessary administrator rights.
Creating 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.
Here, you directly specify the work package‘s type, title, status and story points. The list contains those work package types that are activated for the backlogs plug-in; usually those are Feature and Bug.
In the background, a new work package is created in the project. 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. In order to do so, choose a work package type and target version which are activated in the backlogs-plugin – such as feature or bug, and product or sprint backlog, respectively.
Read more about creating user stories in the backlog view.
You can prioritize different work packages within the product backlog using drag&drop and you can attribute them to a specific sprint backlog.
Note: If you move a work package into the backlogs view, the target version will automatically be adapted in the background.
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.
Read more on assigning and editing the story points.
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.
Note: Apart from start and end date, you can also adjust the sprint name. To do so, you have to be a project administrator.
Note: a backlog version will be shown under Roadmap, but not in a Timeline. 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.