[Fiware-wpa] R: [Fiware-wpl] On priority field in backlog entries (YOUR INPUT IS NEEDED before 17:00)

[Garino Pierangelo]

Hi Juanjo,

for those I2ND wiki pages (i.e. epics) having already a priority defined we used the rule: 1=lowest priority, n=Highest priority (n equals to 4 for MoSCoW, and 5 for relative priority).

So for us priority 34 means 'Should' (3) and nearly highest relative priority (4) for e.g. and Epic.

On the other hand, currently the 'Priority' field in the Forge backlog tickets can take the values: 1=lowest to  5=highest, so I would follow the same coding to avoid mixing rules.

Hence my feedback is:

-          I would avoid using '0' (unless we have to manage this value in sw code...)

-          I would support using 1=lowest to 5=highest priority

-          I would support using the MosSCoW coding: MUST=4, SHOULD=3,COULD=2, WONT=1

BR
Pier







Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro
Inviato: giovedì 10 novembre 2011 07:25
A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu
Oggetto: [Fiware-wpl] On priority field in backlog entries (YOUR INPUT IS NEEDED before 17:00)

Hi all,

  During our last confcall, Pier raised the issue about value of the "Relative Priority" field of entries in the backlog.

  I have checked the template as well as what is currently on the Wiki tutorials (which was based on the template).   It is clear that this field should have the form of a two-digit number of which the first digit has to map to the MoSCoW priority while the second is used as relative priority.

  Note that we are talking about a two-digit number.   Not anything with a colon in between like it could be <moscow-priority-number>.<relative-priority-number>.

  However, I have found that there are two things that are unfortunately ambiguous and we should clarify:

 *   first, whether higher priorities should have a lower digit or not, i.e., does priority1=15 and priority2=21 means that priority1 is higher than priority2 ?  This relates to the question about whether the correct mapping for the first digit should be (MUST=0, SHOULD=1, COULD=2, WONT=3) or (MUST=3, SHOULD=2,COULD=1, WONT=0) and whether the digit for the relative priority should be assigned a higher value for a lower priority.
 *   sencond, whether each digit should start at 0 or 1
  I would go for assigning lower numbers to higher priorities and start with 0, thus mapping MoSCoW priorities as (MUST=0, SHOULD=1, COULD=2, WONT=3) and then assign relative priorities from 0 to 9 being 0 the highest.    For me, it's kind of more intuitive saying that something that has been assigned priority "01" has a higher priority than something that has priority "21" (because means it is first in my "todo" list) but I would go for what the majority has interpreted so far ...

  Question mark is ... what interpretation have you followed in your chapter ?   (in case you haven't passed specific instructions and you believe this field has not been filled, please let us know)

  Please send your response by 17:00 CET today and we'll take the decision that imply less changes on what has already been set on the Wiki.

  I will send an email with the definitive convention to follow based on your responses by EOB today and will add whatever is needed to the tutorials.   If I don't receive a response from you, I will assume you haven't filled this value so far and, therefore, you can live with what gets decided.

  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
Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.

[cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non è necessario.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20111110/6dd3c13f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logo Ambiente_foglia.jpg
Type: image/jpeg
Size: 677 bytes
Desc: logo Ambiente_foglia.jpg
URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20111110/6dd3c13f/attachment.jpg>