[Fiware-i2nd] I: Detailed comments on the I2ND Backlog information available on the Wiki/Tracker

[Garino Pierangelo]

Hi Juanjo,

here is the status of activity about modifications to be done today. You can find my comments below in Green (look for P.G.).
Hope everything is sufficient for producing the expected docs.

BR
Pier

Da: Garino Pierangelo
Inviato: lunedì 14 novembre 2011 09:10
A: 'BANNIZA, Thomas-Rolf'; Woods, Chris; Hans.Einsiedler at telekom.de; 'Defrance Serge'; pasquale.donadio at alcatel-lucent.com
Cc: Heijnen Henk (henk.heijnen at technicolor.com); 'WUENSTEL, Klaus'; Corici, Marius-Iulian (marius-iulian.corici at fokus.fraunhofer.de)
Oggetto: I: Detailed comments on the I2ND Backlog information available on the Wiki/Tracker

Dear All,

As announced on Friday,  here is a list of actions we have to perform to complete the I2ND backlog (tracker + wiki pages wherever required), in order to finalise the second release of FI-WARE product vision.

First of all, you'll see that introduction of Work Items is suggested in some case, so below are the instructions on how to enter WorkItems in the tracker:

-          First of all, I have added the 'WorkItem' as new value available for the field 'Entry type'; you can select it when creating a new ticket.

-          Then, here is the contents of a mail by Juanjo explaining the naming convention (this is an evolution of the naming convention we introduced last week):
Regarding the Id for these backlog entries, you should follow the convention:

    FIWARE.WorkItem.<chapter>.<Generic Enabler>.<Id>

  It is recommended that the <Id> follows a format like [<Epic>.]<Feature>.<WorkItemId> so that the original Epic/Feature the WorkItem relates to can be easily traced.

  I remind you that Work Items do not need to have a full detailed description on the Wiki.   Just a ticket on the tracker, with all fields properly filled.

Back to the list of actions to be performed, you can find it below: I have added a responsible for each of them (yellow highlight), please let me know if this creates troubles to complete by today, and we'll find an alternative solution.
Despite what said in the mail, I'd like that ALL the points are done (both blue and red items) so that we complete once for all the modifications.

Please let me know asap if you have troubles to perform the modifications, thanks.


BR
Pier




Da: Juanjo Hierro [mailto:jhierro at tid.es]
Inviato: lunedì 14 novembre 2011 08:19
A: Hans.Einsiedler at telekom.de; Garino Pierangelo
Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu
Oggetto: Detailed comments on the I2ND Backlog information available on the Wiki/Tracker

Dear Pier and Hans,

  Here it is a list of issues I have identified in a more detailed revision of backlog entries, both on the Wiki and the tracker, linked to your chapter.  You have to review them and take the necessary corrective measure.   Despite I have marked the most critical ones in red, all of them are relevant and shall be addressed.  Many of the issues are rather easy to address.  With the exception of those market in blue, the rest of them might be solved before EOB today if responsibility to fix them is properly distributed and changes are implemented in parallel.   I remind you that sections on the Wiki should be edited in parallel (never clicking on the edit tab at the top of the page but clicking on the edit link at the right side of each section).

  Please forward them to members of your team as soon as possible.

  I copy the rest of the WPLs and WPAs because I haven't sent my detailed comments to all of them and it might be worth that they review your comments to find out what may apply to them as well.   This may help them to anticipate any issue on their respective chapters.

  Best regards,

-- Juanjo


I2ND:

 *   General comments:
    *   Regarding entries linked to Features, you should verify that the "FI-WARE Release Id" field on the tracker is properly filled for all Features you plan to address in the 1st minor release.   This field should also be filled in Features you believe will be addressed in the second minor release
P.G.: This is basically done. For all GEs there is at least one entry scheduled for first minor release, plus some (few!) scheduled for first sprint.


    *   You have used "User-Stories" in the Id of entries linked to some of the User-Stories instead of "Story" as suggested in the template and tutorial.   Since it only applies to two entries, I would encourage you to fix it.  Unfortunately, you would need to implement three changes: 1) rename the Wiki page each entry points to (this can be done using the "move" operation in the Wiki page that corresponds to the backlog entry description) 2) change the name in the list of backlog entries in the "Materializing ..." page and 3) update the URL in the corresponding tickets in the tracker.
P.G.: Done.


 *   Connected Device Interfacing:
    *   I miss the tickets linked to the FIWARE.Feature.I2ND.CDI.Phone.* functionalities as well as

P.G.: Temporarily removed Feature entries from wiki (saved names for re-insertion later).

    *   The FIWARE.User-Stories.I2ND.CDI.DeviceFeatures.CommonDeviceInterface.FrameWorkAndPlatform User-story may probably map better as a WorkItem but you may keep it as a User-Story ... However, I sincerely have some doubts that you can address it during the course of the first sprint (i.e., get it finished by end of November) ...  I would go for replacing it by a set of Work-Items that you can tackle in subsequent Sprints ... Similar comment applies to some other User Stories ...
P.G.: This is not modified (yet), none scheduled for Sprint ID 1.1.1.


 *   Cloud Edge:
    *   Is the FIWARE.Feature.I2ND.CE.HomeResourceAbstractionLayer Feature planned for the first minor release ?  If so, please add the Release Id in the corresponding ticket on the tracker
    *   What do you plan to do in the first Sprint (scheduled to finish by end of November) ?   Need to see some User-Stories or WorkItems planned ...
P.G.: Done some adjustments, maybe a consistency check will be required (people involved currently unavailable, traveling to Berlin, as tomorrow we have the I2ND meeting).

 *   Network Information & Control:
    *   You should replace "EPIC" by "Epic" in the Id of the FIWARE.EPIC.I2ND.NetIC.NetworkResourceControl entry.   Unfortunately, you would need to implement three changes: 1) rename the Wiki page each entry points to (this can be done using the "move" operation in the Wiki page that corresponds to the backlog entry description) 2) change the name in the list of backlog entries in the "Materializing ..." page and 3) update the URL in the corresponding tickets in the tracker.
P.G.: Done.


    *   There are some tickets on the tracker (537, 795, 907, 908) which don't map any entry description on the Wiki and are not linked to Work Items ... Check if you have to delete them.
P.G.: Done.


    *   I miss the tickets linked to the two features listed on the Wiki.   Apparently, one of them maps to a ticket on the tracker but that ticket doesn't follow the convention of using the entry id as the "summary" field of the ticket.   Once you fix this and get the features, don't forget to declare what release they are planned for.
P.G.: Done.

    *   What do you plan to do in the first Sprint (scheduled to finish by end of November) ?   Need to see some User-Stories or WorkItems planned ...
P.G.: WorkItem inserted FIWARE.WorkItem.I2ND.General.AssetRevision<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=963&group_id=10&atid=192> to cope with all GEs in the chapter, scheduled for first Sprint.

________________________________
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/old-fiware-i2nd/attachments/20111114/06163468/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001..txt
URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20111114/06163468/attachment.txt>
-------------- 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/old-fiware-i2nd/attachments/20111114/06163468/attachment.jpg>