[Fiware-i2nd] [Fiware] Wrong numeration schema in the trackers

[Banniza, Thomas-Rolf (Thomas-Rolf)]

Hi Pier,

For sure, I have also seen this part of the mail... But again: you can see from this that FI-WARE lacks continuous and sustainable management and tool support:

1. this is an important piece of info, this should be part of an info page with good visibility (to be observed, this should be linked from the tracker pages); to distribute it like this is, simply spoken, non-professional...

2. the list ends in June, so (from this mail) nobody is able to plan for the rest of year. Does this mean: let's wait for the review, whether we have still to plan for a further period of time? (I hope this is not the case...). Either there is a sustainable numbering scheme, than this should be clearly described, or this mail indicates that numbering is given only on sight distance (would match with TID managament style).

Best regards,
Thomas

________________________________
Von: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it]
Gesendet: Donnerstag, 14. Juni 2012 14:32
An: Banniza, Thomas-Rolf (Thomas-Rolf)
Cc: FiWare WP7 (fiware-i2nd at lists.fi-ware.eu)
Betreff: R: [Fiware] Wrong numeration schema in the trackers

Dear Thomas,
I agree with you (and Thierry) on the fact the naming convention was not adequately 'advertised', so we need to improve the coordination actions.
For what concerns the numbering, the explanation in the mail by F. Aguilar below should dissipate any doubt:
FIWARE.Release.x.y
FIWARE.Sprint.x.y.z    <- Note the x.y digits equal to previous line. z digit restarts at each change of x.y
                  Dic    Ene    Feb    Mar    Apr     May    Jun    Jul    Aug    Sep    Oct    Nov    Dic
Release   1.1     1.1     1.1      1.2      1.2      1.2     1.3
Sprint    1.1.1  1.1.2  1.1.3  1.2.1   1.2.2   1.2.3  1.3.1
Hope it clarifies the issue.
BR
Pier
Da: Banniza, Thomas-Rolf (Thomas-Rolf) [mailto:thomas-rolf.banniza at alcatel-lucent.com]
Inviato: giovedì 14 giugno 2012 10:56
A: Garino Pierangelo
Cc: FiWare WP7 (fiware-i2nd at lists.fi-ware.eu)
Oggetto: WG: [Fiware] Wrong numeration schema in the trackers
Dear Pier,
 do you know of any Wiki page or other doc which definitvely describes the correct naming/numbering/whatever of the various periods (sprints, releases, sub release, ...). If there is no such page, please urgently request such a page from project managament!
We discussed this item early this year (with no result...), and now it comes up again...
Knowing the correct naming doesn't solve the problem of having obviously only 3 user stories for release 1.3 (in whole Fiware I assume, following mail of Thierry Nagellen this morning), but if the managament does not do the basic jobs, it can't expect correct filling of the management tables....
Best regards,
Thomas
________________________________
Von: fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] Im Auftrag von Miguel Carrillo
Gesendet: Mittwoch, 13. Juni 2012 17:14
An: fiware at lists.fi-ware.eu
Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu
Betreff: [Fiware] Wrong numeration schema in the trackers
Dear all,

The information sent by Fernando at the end of this message is of high importance and it has to be understood. We have to use a consistent terminology for Releases and Sprints in the project. We have checked it in the backlog and unfortunately it is not always the case.

I attach the excel file we used to deliver the backlog to the EC, based on a snapshot of the backlog trackers of the chapters taken last Friday. To understand what we mean, you can check the modifications we made to the sprint and release fields by hand on the spreadsheet.

Those chapters who do not have User Stories in Release 1.3 (more precisely, Sprint 1.3.1), are sending the message that they are doing nothing now (hopefully not the case!). Please amend it.

This convention of Releases and Sprints is something general, this means that a given chapter cannot decide autonomously to follow a different schedule/numbering. We need to show a coherent face to the outside world.

I send you this directly as this is of general interest and the WPAs/WPLs are focusing on the upcoming review, it must get to everyone.

Best regards,

Miguel

-------- Mensaje original --------
Asunto:

[FIWARE] Wrong numeration schema in the tracker...

Fecha:

Wed, 13 Jun 2012 12:03:23 +0200

De:

FERNANDO LOPEZ AGUILAR <fla at tid.es><mailto:fla at tid.es>

A:

Irena Trajkovska <irenatr at gmail.com><mailto:irenatr at gmail.com>, Javier Cerviño <jcervino at dit.upm.es><mailto:jcervino at dit.upm.es>, Joaquin Salvachua <joaquin.salvachua at upm.es><mailto:joaquin.salvachua at upm.es>

CC:

MIGUEL CARRILLO PACHECO <mcp at tid.es><mailto:mcp at tid.es>, JUAN JOSE HIERRO SUREDA <jhierro at tid.es><mailto:jhierro at tid.es>, "fiware-cloud at lists.fi-ware.eu"<mailto:fiware-cloud at lists.fi-ware.eu> <fiware-cloud at lists.fi-ware.eu><mailto:fiware-cloud at lists.fi-ware.eu>



Dear Javier and Irena,
I was checking the tracker and I could see some inconsistencies in the
tracker numeration. Please check it taking into account the following
indication.
FIWARE.Release.x.y
FIWARE.Sprint.x.y.z
                  Dic    Ene    Feb    Mar    Apr     May    Jun    Jul    Aug    Sep    Oct    Nov    Dic
Release   1.1     1.1     1.1      1.2      1.2      1.2     1.3
Sprint    1.1.1  1.1.2  1.1.3  1.2.1   1.2.2   1.2.3  1.3.1
Please consider that you cannot have an entry with assigned Sprint in a status Open
should be either Closed or Under Execution.
Please check all your entries in the tracker in order to check it and correct the possible
wrong numeration schema ASAP.
Best regards,
Fernando López Aguilar
Cloud Computing
fla at tid dot es
+34 914 832 729
Telefónica I+D (R&D)
Ronda de la Comunicación s/n
Distrito C, Edificio Oeste 1, Planta 5
28050 Madrid, Spain

[cid:65E3CA3A-3DFE-41B6-8F69-2AD965EA42FA at hi.inet]
________________________________

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:794343612 at 14062012-0C0D]Rispetta l'ambiente. Non stampare questa mail se non è necessario.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20120614/e433770a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logo Ambiente_foglia2.jpg
Type: image/jpeg
Size: 677 bytes
Desc: logo Ambiente_foglia2.jpg
URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20120614/e433770a/attachment.jpg>