Project

General

Profile

Sprint board Sprint burndown (hours) Sprint burndown (SPs) Sprint stats Help

Sprint board help

PBIs & tasks

An Sprint board includes PBIs & tasks. PBIs (or Product Backlog Items) are typically user stories, bugs, technical debts... and they are composed of child tasks. Under Administration » Plugins » Scrum Redmine plugin you can configure which issue trackers are considered PBIs and which are considered tasks.

PBIs are located on the left part of the board, tasks on the right columns. There is a column per possible task status (these statuses are configurable under Administration » Plugins » Scrum Redmine plugin).

A lot of the described features are enabled only with permissions, so take a look to Administration » Roles & permissions » Permissions report to enable/disable permissions for each role.

Working with PBIs

PBIs can be created in this board with the links at the end of the board or moved from the product backlog view.

Once you have PBIs on the Sprint board, you can dragged in vertical to change their order (so the team will start with the ones at the beginning). In the PBI post-it you will see its attributes (to enable more/less attributes take a look to Administration » Plugins » Scrum Redmine plugin). You can edit them clicking on the pencil icon.

PBIs are estimated in story points (SPs), you can edit directly this value clicking on the SPs value and typing a new value (then press ENTER or TAB). If use remaining story points is enabled (under Administration » Plugins » Scrum Redmine plugin) then you will see that field also in the post-it, it's also editable; this is used to calculate a precise Sprint burndown by SPs, so don't forget to update it day by day (before leaving the office).

Working with tasks

Tasks are technical things to be done in order to complete a PBI. They can be created directly clicking on the icon in the PBI post-its (or creating new child issues from the PBI issue form).

To change task status, just drag & drop in horizontal direction (or edit & change its status). Take care of your tracker work flow, because maybe some movements are forbidden for some roles (ask your administrators). There are a few automatic actions involved when you move task post-its (take a look to Administration » Plugins » Scrum Redmine plugin to enable/configure them):

  • When you move the first task from new (first tracker state defined in the admin settings) to any other state, the plugin change parent PBI status to in progress (the second state).
  • When you change a task status to anything but new, and it has not assignee, the plugin set it to current user; if the task is changed to new status, the assignee is removed.
  • When the last task is closed, the remaining effort is set to zero and the parent PBI is changed to a configurable status (i.e. resolved).

Tasks are estimated in hours, using the estimated effort field, this is also editable in the post-it. In order to calculate an Sprint burndown by hours is also necessary to fill the remaining effort field (day by day). You can log time to the tasks clicking on log entry icon.

As soon as you assign a task or log time into it, an orange mini-post-it (color is configurable under Administration » Plugins » Scrum Redmine plugin) is attached to the task, and a green one in case you log review time (review time has also to be configured under Administration » Plugins » Scrum Redmine plugin). This allow to follow up how is doing what easily.


Support this Redmine Scrum plugin

In order to be an open source & free plugin, I need your support:

or

Kindly regards,
Emilio González Montaña

Sprint board

2017-07-18

2017-08-31

16/16
0.0/0.0
0.0%

Product backlog items New In progress Resolved
#1381: Scrum plugin doesn't work with redmine 3.4.x
Category: General
Target version: Scrum v0.18.0
Detected on version: Scrum v0.16.2
#1405: Spent time link on task post-its fails
Emilio González Montaña
#1407: Create and continue button doesn't work
Emilio González Montaña
#1395: Move not closed PBIs to last Sprint
Category: Sprint board
Target version: Scrum v0.18.0
#1396: Add action in Scrum controller to move not closed PBIs
Emilio González Montaña
#1397: Add info about project at PB
Category: Product backlog
Target version: Scrum v0.18.0
#1419: Add info at Sprint views (by settings)
Emilio González Montaña
#1433: PB stats must render all selected projects stats
Emilio González Montaña
#1432: Add Sprint stats at Sprint views
Category: Sprint stats
Target version: Scrum v0.18.0
#1434: Add Sprint stats
Emilio González Montaña
#1399: Permission to see/edit pending effort
Category: Issues list & form
Target version: Scrum v0.18.0
#1400: Add & apply permission
Emilio González Montaña
#1402: Closed SPs per Sprint chart
Category: General stats
Target version: Scrum v0.18.0
#1404: Improve readability when there are a lot of Sprints
Emilio González Montaña
#1408: Consider PBI as closed in Sprint burndown if child tasks are closed
Category: Sprint board
Target version: Scrum v0.18.0
#1412: Add setting & patch Issue.closed?
Emilio González Montaña
#1416: Update feature to affect (only) Sprint burndown
Emilio González Montaña
#1417: Error rendering Sprint burndown by SPs if no Sprint dates
Category: Sprint burndown
Target version: Scrum v0.18.0
Detected on version: Scrum v0.18.0
#1418: Check not empty data
Emilio González Montaña
#1406: Filter PB, PB burndown & release plan by project
Category: Product backlog
Target version: Scrum v0.18.0
#1420: Show project in post-its when post-it project is different to actual
Emilio González Montaña
#1421: Add filter by project on PB board view
Emilio González Montaña
#1422: Add filter by project on PB burndown view
Emilio González Montaña
#1423: Add filter by project on PB relase plan view
Emilio González Montaña
#1409: Add remaining SPs & use it to calculate burndown
Category: Sprint burndown
Target version: Scrum v0.18.0
#1430: Add plugin setting for using remaining SPs & use it in Sprint board
Emilio González Montaña
#1431: Use remaining SPs to calculate Sprint burndown
Emilio González Montaña
#1410: PB burndown with child projects breakdown
Category: Product backlog
Target version: Scrum v0.18.0
#1425: Add one burndown per project + all projects one
Emilio González Montaña
#1427: Add legend to show the project & graph color
Emilio González Montaña
#1429: Improve burndown graph when there are a lot of child projects
Emilio González Montaña
#1442: Limit graph when a lot of child projects exist
Emilio González Montaña
#1411: Sprint burndown with child projects breakdown
Category: Sprint burndown
Target version: Scrum v0.18.0
#1443: Calculate Sprint burndown by SPs with remaining SPs (if enabled)
Emilio González Montaña
#1435: Plugin ignores settings for rendering fields
Category: Settings & admin
Target version: Scrum v0.18.0
Detected on version: Scrum v0.18.0
#1436: Review issue attributes form in post-it pop-up partial view
Emilio González Montaña
#1437: Error on project Scrum stats with nil dates
Category: General stats
Target version: Scrum v0.18.0
Detected on version: Scrum v0.18.0
#1438: Add extra code checks
Emilio González Montaña
#1439: Multiproject improvements
Category: General
Target version: Scrum v0.18.0
#1440: Add project selector to PBI/task edition
Emilio González Montaña
#1441: Render project name if different to current in tasks in Sprint board
Emilio González Montaña
#1444: Test & make current version stable
Category: General
Target version: Scrum v0.18.0
Detected on version: Scrum v0.18.0
#1445: Fix PBI creation on PB
Emilio González Montaña
#1446: Fix PB & Sprint burndowns on old Redmine versions
Emilio González Montaña
#1447: Review closed? usage for PBIs (setting -> consider PBI closed if tasks are closed)
Emilio González Montaña
#1448: Fix project filed in PBIs of child projects
Emilio González Montaña
#1449: Simplify series on only project burndowns
Emilio González Montaña
#1450: More protections & strange cases fixing
Emilio González Montaña