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:

Patreon logo or Paypal logo

Kindly regards,
Emilio González Montaña

Sprint board

23/10/2017

07/11/2017

Product backlog items New In Progress Feedback Closed
#2168: Drag and drop de produit vers SciQlop
Story points: 2
sp rsp 0h
#2171: Drag depuis les datasources
blocked: No
#2176: Drop de produits dans les variables
blocked: No
#2169: Drag and drop de variable vers visu
Story points: 2
sp rsp 0h
#2166: Drop de variables dans la visu
blocked: No
#2172: Drag depuis les variables
blocked: No
#2170: Drang and drop de timeWidget <-> SciQlop
Story points: 3
sp rsp 0h
#2173: Drag depuis le timeWidget
blocked: No
#2174: Drop vers le timeWidget
blocked: No
#2177: Implémentation du Drag and Drop dans la visualisation
Story points: 6
sp rsp 0h
#2178: Drag and drop de visu vers visu
blocked: No
#2253: Drag and drop entre 2 tabs
blocked: No
#2180: API Spectro
Story points: 8
sp rsp 0h
#2219: Document d'architecture API Spectro
blocked: No
#2181: Initialisation API Catalogue
Story points: 2
sp rsp 0h
#2190: Initialisation dépot git
blocked: No
#2191: Configuration API avec QMake et QxOrm
blocked: No
#2182: Moteur de recherche
Story points: 3
sp rsp 0h
#2192: Implémentation de l'API du moteur de recherche
blocked: No
#2193: Imp méthode request Du CatalogueDao
blocked: No
#2194: Test unitaire méthode moteur de recherche
blocked: No
#2183: CRUD Event
Story points: 2
sp rsp 0h
#2195: Imp modele event
blocked: No
#2196: ajout d'un Event
blocked: No
#2197: Récupération d'un Event
blocked: No
#2198: Modification d'un Event sans effet de bord
blocked: No
#2199: Suppression d'un Event (sans effet de bord)
blocked: No
#2184: CRUD Catalogue
Story points: 2
sp rsp 0h
#2200: Imp modèle catalogue
blocked: No
#2201: Ajout d'un catalogue
blocked: No
#2202: Modification d'un catalogue
blocked: No
#2203: Récupération d'un catalogue
blocked: No
#2204: Suppression d'un catalogue
blocked: No
#2205: Récupération des Events d'un catalogue
blocked: No
#2185: CRD Tag
Story points: 2
sp rsp 0h
#2207: Imp modèle Tag
blocked: No
#2208: Ajout d'un Tag
blocked: No
#2209: Récupération des Tags
blocked: No
#2210: Suppression d'un Tag
blocked: No
#2186: Lien Event, Catalogue, Tag
Story points: 3
sp rsp 0h
#2206: Effet de bord Event sur Catalogue
blocked: No
#2188: Méthodes liées au DB
Story points: 2
sp rsp 0h
#2215: Ajout d'un DB
blocked: No
#2216: Sauvegarde d'un DB
blocked: No
#2226: Représentation des spectrogrammes
Story points: 1
sp rsp 0h
#2227: Création de la classe SpectrogramSeries
blocked: No
#2230: Génération d'un spectrogramme (plugin bouchon)
Story points: 3
sp rsp 0h
#2231: Ajout d'un produit représentant un spectrogramme dans le plugin bouchon
blocked: No
#2232: Affichage du spectrogramme bouchon dans un graphe
blocked: No