[Fiware-apps] Review of Apss Backlog

[Fasse, Axel]

Dear Partners,

To be more precise - and to avoid any kind of confusion - I want to mention, we are formally in Sprint 2.2.2.
Because of this, everything (Sprint 2.2.1 or older must be closed) and topics for release 2.2.3 (or higher) should/could be open.
Please take this into accout to avoid any additional Review-Loops.

Otherwise we are not able to demonstrate our agile approach.


Best ragards,
  Axel

From: Fasse, Axel
Sent: Freitag, 15. Februar 2013 09:41
To: 'fiware-apps at lists.fi-ware.eu' (fiware-apps at lists.fi-ware.eu)
Subject: FW: Review of Apss Backlog
Importance: High

Dear Partners,

Miguel has finalized his review of our contributions to the upcoming deliverables.
The XLS File contains different tabs (see the explanation from Miguel). Please take into account the complete information.
It is very important for us to provide a complete and consistent picture of our work.



·         Please check and correct the documented misleading between the materializing - page and the backlog tracker

·         Please provide the missing content

·         Follow the naming conventions

o   An Introduction about the usage of the Tracker and the information that should be provided during the creation phase for a new entry is documented under http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_create_entries_in_the_%22Backlog_Management%22_Tracker_of_a_FI-WARE_Chapter

§  Naming-Conventions for releases and sprint are defined under Releases and Sprints numbering<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering>#

§  Please take into account that we are talking about release two. Some of the entries seems to be related to Release one. We have to ensure that we make transparent what's coming next (Release two). It's important to use the right numbering!! Please correct this accordingly and consistent!

§  Please also refer to the following Links to avoid any kind of additional re-work afterwards.

·         http://wiki.fi-ware.eu/How_to_assign_identifiers_to_FI-WARE_Backlog_entries_(convention_to_follow)

·         http://wiki.fi-ware.eu/How_to_upload_the_full_description_of_backlog_entries_to_the_Wiki

·         http://wiki.fi-ware.eu/How_to_create_entries_in_the_%22Backlog_Management%22_Tracker_of_a_FI-WARE_Chapter

·         Some additional Hints

·         Please take into account, that an entry within the tracker is marked as closed, if the related work is done!!

·         So please check the usage of "open/closed.../" within tab 2 of the xls file

·         If entries within the tracker are no longer relevant, we have to think about the idea to delete them

·         If you delete entries, this should be reflected accordingly in des complete system landscape!! (WIKI, TRACKER, ...)

·         You can check the available information at tab 3. you can use this content to identify the open issues that you have to take care about-


On the first tab of the XLS file you can find a complete todo-list with all of the open issue that we have to take care about.

I know that this is a "long" list of topics - some of them could be fixed within seconds - that we have to take into account.
But for each of the partner it should not be too much work to handle and finalize this within this week.
I would expect, that TID will ask for a valid update on Monday.
Please let me know if you need more time.

If you have any kind of questions, please contact me directly.

Best regards,
  Axel

From: Miguel Carrillo [mailto:mcp at tid.es]
Sent: Mittwoch, 13. Februar 2013 16:35
To: Fasse, Axel; Leidig, Torsten
Cc: JUAN JOSE HIERRO SUREDA
Subject: Review of Apss Backlog

Dear Axel&Torsten,

I enclose my review. It is high level as it would take years if I did it in low level detail .

My main concerns are:

1) Misalignment between entries in "materializing ..." and the backlog tracker
2) Lazy edition of wiki records of epic/features (for instance, empty fields)
3) Lack of compliance with naming conventions

The excel file I enclose has a sheet with the processed data ("WP3- Apps & Svcs") and then another sheet with the contents of my review ("Apps GEs in R2") . There is also a sheet with the source data ("apps_raw") in case this is needed.

This deliverable will be sent to the EC chapter by chapter, separately. The Apps deliverable will not be sent to the EC until these objections have not been solved or properly justified.

Best regards,

Miguel


--

----------------------------------------------------------------------

     _/          _/_/                     Miguel Carrillo Pacheco

    _/   _/     _/  _/   Telefónica       Distrito Telefónica

   _/ _/_/_/   _/   _/   Investigación y  Edifico Oeste 1, Planta 4

  _/   _/     _/  _/     Desarrollo       Ronda de la Comunicación S/N

 _/          _/_/                         28050 Madrid (Spain)

                                          Tel:  (+34) 91 483 26 77



                                          e-mail: mcp at tid.es<mailto:mcp at tid.es>



Follow FI-WARE on the net



        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

----------------------------------------------------------------------

________________________________

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/20130215/758704fd/attachment.html>