Dear Thierry,
We are in the same boat for sure, but let me raise a number of points:
* The deliverable linked to the snapshot of the backlog corresponds to a snapshot taken on June 8th. That could be a good rationale for explaining that there are few User Stories linked to the last Sprint being included in the snapshot. We may easily argue that teams had not yet registered in their backlogs the User Stories for the Sprint at the time the snapshot was taken.
* However, the major issue is not that. The major issue is that if you make a careful analysis of the backlog snapshot you simply find out that several of the chapters, had stopped recording their activities in the backlog since approx. January. This, honestly, is a REAL ISSUE. Should we (or can we) hide that ?
* An easy exercise (which reviewers most probably will perform) would be to compare the first backlog snapshot that were generated in December (after the first sprint, but including some backlog entries in second Sprint) with the backlog generated the first week of June. 1,5 to 2 times the number of entries in the snapshot taken in December should have been there in the snapshot of June compared to the snapshot in December:
* Apps Chapter evolves from 78 entries to 105 entries (34,6% more)
* Cloud Chapter evolves from 165 entries to 305 entries (84% more)
* IoT Chapter evolves from 128 to 134 entries (4,6% more)
* Data Chapter evolves from 93 entries to 157 entries (68,8% more)
* I2ND Chapter evolves from 55 entries to 89 entries (61,8% more)
* Security Chapter evolves from 72 entries to 76 entries (5,55% more)
Given the risk that these facts can be easily detected by the reviewers, I believe we should at least prepare an answer. In this respect, I would like to assign the following APs:
* The IoT Chapter and the Security Chapter should elaborate on why only 6 and 4 entries, respectively, have been added to the backlogs in 6 months of activity (from December 2011 until end of May 2012). They definitively have to come back with a plan explaining how they will be able to recover.
* Activity in the backlog by the Apps Chapter seems to be too low ... It would be nice to find out the reasons why. We haven't analyzed whether this is because the rate of entries planned at each Sprint is lower than in other chapters (e.g., Cloud) or it has been a matter that hey have stopped planning Sprints properly and recording the planning in the backlogs since some given month. Please provide an answer to that and identify some APs that will lead to improvements.
* Activity recorded in the IoT Chapter and Data Chapter backlogs may be justifiable, but it would be worth carrying out some sort of analysis to identify whether there may be GEs about which no activity is being recorded and find areas of improvement. Please carry out that analysis and identify some APs for improvement.
* Activity in the Cloud Chapter backlogs seem to be overall ok. Nevertheless, it would be nice that you carry out an analysis that still lead to identification of some APs for improvement.
We should prepare a slide or two with the list of APs identified from this analysis. We will present it in case that any reviewer comes with questions based on some facts like the ones I have highlighted above. Nevertheless, after review, we should work on how to implement the identified APs.
Obviously a lesson on our side (TID) is that we have to monitor progress of the backlogs more closely to avoid surprises like these ones. One of the actions that I identified was that of creating a dedicated team (Miguel Carrillo will lead it, Axel Fasse will be part of that team) which will monitor progress in the backlogs, at least identifying any problematic symptoms. Unfortunately, we hadn't implement that action (we only kicked off the activities of the dedicated team that was taking care of UC project tickets)
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 14/06/12 09:55, thierry.nagellen at orange.com<mailto:thierry.nagellen at orange.com> wrote:
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> [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<mailto:fiware at lists.fi-ware.eu>
Cc : fiware-wpl at lists.fi-ware.eu<mailto:fiware-wpl at lists.fi-ware.eu>; fiware-wpa at lists.fi-ware.eu<mailto: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.
_______________________________________________
Fiware-wpa mailing list
Fiware-wpa at lists.fi-ware.eu<mailto:Fiware-wpa at lists.fi-ware.eu>
http://lists.fi-ware.eu/listinfo/fiware-wpa
________________________________
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/fiware-wpa/attachments/20120614/41012a50/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy