[Fiware-wpl] Detailed comments on the I2ND Backlog information available on the Wiki/Tracker

Juanjo Hierro jhierro at tid.es
Mon Nov 14 08:18:46 CET 2011


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.
    *   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.
 *   Connected Device Interfacing:
    *   I miss the tickets linked to the FIWARE.Feature.I2ND.CDI.Phone.* functionalities as well as
    *   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 ...
 *   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 ...
 *   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.
    *   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.
    *   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.
    *   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 ...

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


More information about the Fiware-wpl mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy