[Fiware] Wrong numeration schema in the trackers (IMPORTANT UPDATE)

[Juanjo Hierro]

Dear all,

   Unfortunately, we made a mistake with the numbering of Releases and Sprints in our previous mail sent by Miguel Carrillo.   We apologize for that and thanks to Alex Glikson for pointing it out.    Sprints actually started in November 2011.   Therefore, the right Sprint numbers until April are the following:

Nov 11: 1.1.1
Dec 11: 1.1.2
Ene 12: 1.1.3
Feb 12: 1.2.1
Mar 12: 1.2.2
Abr 12: 1.2.3

  As you know, we have extended the duration of the development of the first Release until end of June, and we should be consistent with that.   This means that we should have planned three additional Sprints, entering into a 1.3 Minor Release, regarding activities linked to those GEs that will be delivered by end of June and will be available on the FI-WARE Testbed by end of July:

May 12: 1.3.1
Jun 12: 1.3.2
Jul 12: 1.3.3

  The Sprint in July (1.3.3) should be focused on carrying out activities linked to setup the delivered GEs in the FI-WARE Testbed (these activities typically to be registered in the backlogs as Work Items).   During that Sprint, you may also plan some last-minute developments.

  Note that Features that we may have planned for a given minor release (e.g., release 1.2) but couldn't be implemented by end of that minor release should be replanned for a future minor release, typically the next one if it were a matter of lacking of time (wrong estimation).   We should have followed this rule during your development.    You should always reflect such re-plannings by means of updating the ReleaseId field in the re-planned Features.  The release id of a given Feature should always identify the Minor Release at which it is planned that all developments linked to implementation of the Feature have been completed (therefore the feature is completely supported in the product).   This means that if you hadn't finished the development of Feature X in release 1.2, which is when it was initially planned, you should update the release id of Feature X to become release 1.3.

  Note also that we announced that some features of some of the GEs initially planned for the 1st Major Release would not be available on the Testbed until end of September.   These means that we have extended duration of the development for those GEs and, again, we should be consistent with that.   For such GEs, the Sprint numbering we suggest to follow in the period from start of July until end of September is the following:

Jul 12: 1.3.3
Aug 12: 1.4.1
Sep: 1.4.2

  There are GEs that will be delivered as part of Major Release 1 but will further evolve in Major Release 2.   When do activities for Release 2 start for such GEs ?

  *   They will start in August for those GEs that will make available all features planned for Release 1 by end of July in the FI-WARE Testbed
  *   They will start in October for those GEs that will make available all features planned for Release 1 by end of September in the FI-WARE Testbed


  In order to make sure that numbering of all Sprints linked to the 2nd Major Release get synchronized for all GEs from October on, we suggest to adopt the following numbering of Sprints:

Aug 12: 2.0.1
Sep 12: 2.0.2
Oct 12: 2.1.1
Nov 12: 2.1.2
Dec 12: 2.1.3

  Note that during August and September, there will be some GEs that will be running Sprints numbered as 1.4.1 and 1.4.2, while there will be GEs that will be running Sprints numbered as 2.0.1 and 2.0.2.  This should all be natural because this simply reflects that the developments under 1.4.1 and 1.4.2 are officially part of Release 1, to be made available on the Testbed by end of September, while developments under 2.0.1 and 2.0.2 are officially part of Release 2.

  We will not allow updates of the FI-WARE Testbed linked to Release 2 developments until end of October 2012.  Those updates would integrate results of Sprint 2.1.1 in all cases and, for those GEs whose development had started earlier in August, those updates should also incorporate results from Sprints 2.0.1 and 2.0.2.   The idea is to allow upgrades of the FI-WARE Testbed every Sprint following an Agile approach from then on.   Note, however, that updating the software that implements a given GE will not be mandatory at the end of each Sprint during Release 2, it would be just optional (some GE owners may be interested in this to gather feedback from UC projects as early as possible).    Updating the software at least every minor release (i.e., every three months) would be the default option.

  There are some GEs for which development have started earlier than August 12.   No problem if you followed the numbering linked to Sprints under Release 1 until that month.   From August on, just adopt the numbering suggested above for Sprints linked to Release 2.

  Please make sure you keep consistent with this overall numbering of Releases when updating trackers linked to your chapter.

  We will document all this on the Wiki, so this info becomes available at any time.   Thanks to those who raised the need for doing so.

  Best regards,

-- Juanjo


-------------
Product Development and Innovation (PDI) - Telefonica Digital
website: www.tid.es<http://www.tid.es>
email: jhierro at tid.es<mailto:jhierro at tid.es>
twitter: twitter.com/JuanjoHierro

FI-WARE (European Future Internet Core Platform) Chief Architect

You can follow FI-WARE at:
  website:  http://www.fi-ware.eu
  facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
  twitter:  http://twitter.com/FIware
  linkedIn: http://www.linkedin.com/groups/FIWARE-4239932


On 13/06/12 17:13, Miguel Carrillo wrote:
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



_______________________________________________
Fiware mailing list
Fiware at lists.fi-ware.eu<mailto:Fiware at lists.fi-ware.eu>
http://lists.fi-ware.eu/listinfo/fiware


________________________________

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware/attachments/20120614/85322dc1/attachment.html>