[Fiware-wpa] On assignment of tracker tickets and creation of tasks

[Juanjo Hierro]

Hi Folks,

   The Wiki and the trackers are at top speed because of teams working
hard on reaching the milestone on Wednesday, so congratulations.   Hope
it will be definitively reached.

   I would like to send this email to answer some questions regarding
assignment of tickets and creation of tasks.   I believe we should
follow same conventions and practices, that's the reason for this email.

   First of all, I suggest that we deal with development tasks (i.e.,
task derived from taking care of entries in the backlog) in the pure
sense of Agile, i.e., in the course of a sprint.    Since we haven't yet
started the first sprint (it will start on Nov 1th) ... please don't
create development tasks yet.   We will forward you concrete and precise
hints on when/how to create tasks and what Task subprojects to create
linked to your Chapter Projects maybe in one week.   Of course, detailed
tutorials will be provided then.

   This doesn't prevent you to assign tickets to people in your teams so
that they can deal with them and you can organize the work.   You shoud
all have "Admin" role in your respective project, thus owning
"Tech&Admin" privileges on the Backlog Management tracker.   Note that
the rest of the team in your projects, who have the "FI-WARE Chapter
Project Member" role, are even able to reassign tickets while rest of
FI-WARE project members that have the "FI-WARE Project Member" Role will
only be able to solve/handle the tickets (if you have followed the
suggestions made on the tutorials).   You may decide to decide to assign
different privileges at your will, all that is explained on the tutorial.

   Some of you wish to assign tickets to some members of your Chapter
team so that they keep working on them, either refining them (and
eventually produce Features or User-Stories) or just providing
additional info that is currently missing.   Let's use the assignment
operation supported by trackers for the time being and not create tasks
yet.   Tasks linked to Backlog entries are rather easy to create (you
just need to build a task relation to a ticket) and can be useful to
monitor progress of an assignment at a rather fine-grain level, i.e.,
monitoring % of progress and hours devoted, but we have to think
carefully what conventions we should all follow in order to achieve some
level of homogeneity across the project.

   Don't hesitate to ask if you have any further question.

   Best regards,

-- Juanjo

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at.
http://www.tid.es/ES/PAGINAS/disclaimer.aspx