SciQLOP - Redmine

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 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 .

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 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 .

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:

Kindly regards,
Emilio González Montaña

Sprint board

Sprint:

Start date: 28/08/2017

End date: 22/09/2017

Filter by assignee:

Product backlog items

New

In Progress

Feedback

Closed

#1276: Configuration du serveur AMDA Story points: 3
sp rsp

#1972: Générer des std::vector pour les résultats AMDA blocked: No

#1298: Duplication d'une variable Story points: 2
sp rsp

#1784: Duplication d'une variable blocked: No

#1297: Renommage d'une variable Story points: 1
sp rsp

#1785: Renommage d'une variable blocked: No

#1918: Nouvelles taches provenant du sprint précédent Story points: 13
sp rsp

#1919: Sciqlop sur MAC blocked: No

#1920: Mock rampe blocked: No

#1921: Widget de configuration du mock blocked: No

#1923: Appliquer la tolérance au chargement de la variable blocked: No

#1926: Epuration visualisation blocked: No

#1957: Correction diverses sur l'IHM blocked: No

#1929: Acquisition de données Story points: 13
sp rsp

#1932: Barre de chargement dès le début de la requete blocked: No

#1933: Indiquer pour une variable que les données ne sont pas présentes blocked: No

#1936: Vérifier le paramétrage de la synchronisation blocked: No

#1937: Implémenter l'annulation de requete blocked: No

#1938: Implémenter la progression d'une requete blocked: No

#1949: Affiner les étapes de téléchargement de la progress bar blocked: No

#1950: Analyse et correction de la perte de synchronisation blocked: No

#1951: Test d'acquisition de données pour le Cosinus Provider Story points: 2
sp rsp

#1952: Test d'acquisition de données pour le Cosinus Provider blocked: No

#1953: Correction des problèmes de fluidité de SciQlop Story points: 8
sp rsp

#1927: Optimisation du merge de DataSeries blocked: No

#1955: Valider la suppression de variables blocked: No

#1956: Corriger les calculs intempestifs des données tStart/tEnd d'une variable blocked: No

#1963: Optimisation du setDataSeries() d'une variable blocked: No

#1964: Corriger les appels intempestifs de la méthode merge() blocked: No

#1966: Améliorer l'affichage de données blocked: No

#1967: Limiter le nombre de requêtes générées blocked: No

#1968: Corriger le problème de lenteur à l'ouverture d'une variable blocked: No

#1969: Améliorations sur le widget de variables Story points: 3
sp rsp

#1970: Ajouter une colonne "Nombre de points" blocked: No

#1971: Protéger la communication entre le widget et le contrôleur blocked: No

Project

General

Profile

LPP » INSTRU » QLop » SciQLOP