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