[Fiware-apps] Detailed comments on the Apps Backlog information available on the Wiki/Tracker

[Heller, Markus]

Dear Colleagures in WP3,

As indicated by Juanho: please go through the list of issues and comments raised by Juanho and address each if they fit to your organization.

In particular:

-          Please remove deprecated entries (there are some e.g. https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=55&group_id=12&atid=181 from author Nazila Gol mohammadi)

-          Please check that for your entries in WIKI and tracker the description field is not empty. Please add a description if needed.

-          Please check for errors and ensure that what you have committed for sprint 1 is correctly written down in tracker/wiki.

Please do the modifications directly on your own in WIKI and tracker. Please be aware that WIKI has some issues with multiple authors for the same wiki page at the same time and act accordingly.

Please contact me in case of problems.

With best wishes
Markus Heller


From: Juanjo Hierro [mailto:jhierro at tid.es]
Sent: Montag, 14. November 2011 06:54
To: Friesen, Andreas; Leidig, Torsten
Cc: Heller, Markus; Bohnert, Thomas Michael; fiware-apps at lists.fi-ware.eu
Subject: Detailed comments on the Apps Backlog information available on the Wiki/Tracker

Dear Andreas, Torsten, Markus,

  Here it is a list of issues you have to review regarding backlog entries both on the Wiki and the tracker.   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 that 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).

  I copy the FI-WARE Apps team so that they receive the comments as soon as possible and start to analyze them.   They should wait for your further instructions regarding those issues for which they find that the action to be done is not that clear or too hard to implement.

  Best regards,

-- Juanjo

Apps/Services Ecosystem and Delivery:

 *   General comments:
    *   There are some tickets on the tracker that may need to be deleted ... apparently they do not match any entry on the Wiki (e.g., one with summary="Service Assembly" issued by Nazila Gol mohammadi)
    *   The language used for describing goals in the template defined in August for backlog entries has not been followed in many cases.   Some people may argue that description of goals doesn't follow the standard Agile conventions.   Such conventions try to emphasize what the users will get in terms of functionality.
    *   You refer to "Model Repository" and on the tracker, while talking about "Service Repository" and "Registry" on the Wiki.   Please fix this and keep one single vocabulary.   BTW, whatever terms you finally decide to go should also be used accordingly in the FI-WARE Product Vision.
    *   Are you sure that you are going to get all what you have labeled as "STORY" finished by end of the first Sprint (i.e., end of November) ?   When planning a Story like FIWARE.STORY.Apps.Repository.UploadServiceDescription in the first Sprint ... Are you considering not just the specification of the final interfaces to be supported by the baseline asset or even its implementation?   If it was just the specification, probably you need to translate Stories into Features and then define a work-item linked to creating the interface specifications that you can address in the first Sprint.
    *   The "Description" field of some backlog entries on the Wiki is empty.   This is not acceptable.
    *   There are some tickets on the tracker that have assigned an Id which doesn't map the convention "FIWARE.<backlog-entry-type>.Apps.<Generic Enabler>.<Id>" ... are they deprecated entries that were created long time ago as some kind of test of the tracker ?   If so, please delete.
    *   All entries that have been planned for the first Sprint, should have "FIWARE.Release.1.1" as value of the "FI-WARE Release Id" in the tracker.
    *   You have capitalized all letters of the <backlog-entry-type> field in backlog entry Ids, that is, (EPIC, FEATURE, STORY) instead of (Epic, Feature, Story).   While not super-critical it leaves a bad impression and it would be better to fix it.  The issue here is that 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) 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.   Not so hard if the task is distributed, otherwise is a bit painful.
 *   USDL:
    *   There is one entry that is labeled as to be address in Sprint FIWARE.Sprint.1.1.2.   This would not be consistent with Agile principles: you can only plan what user-stories/work-items will come in the current (or about to start) sprint.   You never plan what will go in following sprints.   Maybe it's a typo ...
    *   Regarding the only feature that has been identified ... it sounds like a bit strange that you declare as goal "The feature will provide basic description elements for services including general information, composition, simple pricing and service level agreements." ... saying "USDL will provide basic description elements ..." instead, sounds a bit more appropriate.
 *   Model Repository:
    *   There is a ticket for which I haven't found a correspondence on the Wiki: FIWARE.STORY.Apps.Registry.RegisterStore
    *   A typo in ticket "FIWARE.STORY.Apps.Repository.RetrieveServiceDescription".   You have FIWARE.1.1.1 instead of FIWARE.Sprint.1.1.1 as Sprint Id.
    *   The goals in some tickets are defined as "TBD".   You just need to copy&paste the goal of the corresponding entry on the Wiki.
    *   There is an backlog entry described on the Wiki but without ticket on the tracker
 *   Registry:
    *   I miss a ticket on the tracker linked to the FIWARE.STORY.Apps.Registry.RegisterStore entry on the Wiki
    *   I'm afraid there is a typo and should read "has" when you say: "Provider information will also be described using a Linked Data vocabulary, which have to be defined." in FIWARE.STORY.Apps.Registry.LDProviderSpecification
    *   What's the difference between the FIWARE.STORY.Apps.Registry.LDProviderSpecification and the FIWARE.STORY.Apps.Registry.RegisterProvider ?  Reading the goal is hard to say.
 *   Marketplace:
    *   The goal in some tickets is defined as "TBD".   You just need to copy&paste the goal of the corresponding entry on the Wiki.
    *   I believe that comprising all functions to be supported by the Marketplace in a single "Feature" is too much.   It had been more elegant to have a separate feature per each function (Offering, Storing, Rating, Review, Search, Discovery, Comparison, Analytics, Monitoring).   As highlighted as general comment, It is not clear whether each Story identified as FIWARE.STORY.Apps.Marketplace.<function>API refers to just specification of the API or even the implementation of such API.   Are you going to complete both the specification and implementation within the 1st Sprint (i.e., end of November) ?   If it was just trying to cover the specification of the API, it had been better to turn each Story identified as FIWARE.STORY.Apps.Marketplace.<function>API into a Feature identified as FIWARE.Feature.Apps.Marketplace.<function> planned for the first minor release (note that we have dropped the "API" in the last part of the Id) and then create a Work-item (you just need to create the ticket, not the description on the Wiki) identified as FIWARE.WorkItem.Apps.Marketplace.<function>API planned for the first Sprint.
    *   The ticket linked to the FIWARE.STORY.Apps.Marketplace.OfferingAPI entry seems to be repeated, please delete one.
 *   Store:
    *   Where are the tickets on the tracker linked to these entries ?   Apparently, the Store is not listed among the set of FI-WARE Generic Enablers (see set of valid values of this field in the tracker)
 *   BM&BE Provisioning System:
    *   Where are the tickets on the tracker linked to these entries ?   Apparently, the Store is not listed among the set of FI-WARE Generic Enablers (see set of valid values of this field in the tracker)
 *   Revenue Settlement and Share System:
    *   For a matter of consistency across all entries in the backlog, you should drop the term "Goal" in the Description within the tracker.
    *   Comment general above (similar to the one given for the markeplace) also applies here: please confirm that those stories planned for 1st Sprint do not just deal with definition of interface specifications
 *   Composition:
    *   Apparently, lots of entries whose description is available on the Wiki do not have a corresponding ticket on the tracker.
    *   This is more fundamental: there are several Composition technologies considered here.   I rather believe each should have been categorized as an independent Generic Enabler, with its own backlog.   Why should we mix the backlog linked to the Ericsson Common Composition Engine with the backlog linked to the WireCloud Mashup Platform ?   Maybe it's too late to get this fixed for the official review but deserves discussion.   If agreed with the change, I can live without updating the contents of the FI-WARE Vision (Apps/Services Ecosystem and Delivery chapter) but establishing the distinction between the different GEs within the "Materializing Applications/Services Ecosystem and Delivery in FI-WARE" page on the Wiki.
 *   Mediation:
    *   Where are the tickets on the tracker linked to these entries ?   Apparently, the Store is not listed among the set of FI-WARE Generic Enablers (see set of valid values of this field in the tracker)
 *   SLA Management:
    *   Where are the tickets on the tracker linked to these entries ?   Apparently, the Store is not listed among the set of FI-WARE Generic Enablers (see set of valid values of this field in the tracker)
 *   Multi-channel/Multi-device Access System:
    *   Where are the tickets on the tracker linked to these entries ?   Apparently, the Store is not listed among the set of FI-WARE Generic Enablers (see set of valid values of this field in the tracker)



________________________________
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-apps/attachments/20111114/297f8997/attachment.html>