[Fiware] Wrong numeration schema in the trackers

[thierry.nagellen at orange.com]

Dear all,

Maybe I missed some emails before but I have some difficulties to understand why we have this email now, just 5 working days before the review when no action was planned before. I'm fully aware that we are on the same boat but we have to deeply improve our management of what we have to deliver. Basically, there are only 3 User Stories for release 1.3 (Sprint 1.3.1) which shows clearly that we cannot meet our objectives to give a good picture to the reviewers.

We will do our best to achieve "something" but it cannot be consistent and it would just be some marketing action for the deliverable.

BR

Thierry

De : fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] De la part de Miguel Carrillo
Envoyé : mercredi 13 juin 2012 17:14
À : fiware at lists.fi-ware.eu
Cc : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu
Objet : [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

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware/attachments/20120614/1c809781/attachment.html>