[Fiware-data] FW: [Fiware-demo] Live Demo evolution kick-off

[SERGIO GARCIA GOMEZ]

FYI

From: fiware-demo-bounces at lists.fi-ware.eu [mailto:fiware-demo-bounces at lists.fi-ware.eu] On Behalf Of Fermín Galán Márquez
Sent: Thursday, March 14, 2013 1:52 PM
To: fiware-demo at lists.fi-ware.eu
Subject: Re: [Fiware-demo] Live Demo evolution kick-off

Hi,

Please, find in the following URL the document that was used to define Live Demo Release 1:

https://docs.google.com/document/d/1DhFz9JLJ211ZXNIXUYNEdKyp0HdX46rEFWxn_B2XRWU/edit

However, take into account that this document was abandoned in some point during Live Demo Release 1 preparation, so it is not completely in sync.

Best regards,

------
Fermín

El 14/03/2013 10:39, Fermín Galán Márquez escribió:
Hi,

As discussed during WPL/WPA weekly calls (see https://docs.google.com/document/d/1VpWyuWl44m22l-swR1aQK1tsyZMoiIQCfrdWTPZvub8/edit#heading=h.a4ogm75ss3zu), this list has been created to discuss Live Demo evolution. I have been appointed to lead this cross chapter task force.

As you know, a first version of this Live Demo (let's name it "Live Demo Release1") was successfully performed during second year review at the end of 2012. Our goal now is to evolve an enrich this demo, to be used not only during the next review but also in any moment we need to show the work we are doing in FI-WARE project.

We will be using here the same Agile methodology that we use in the rest of the project (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Agile_Development_Methodology). We will have a backlog associated to the Live Demo. Topics not include in the backlog will not be discussed or taken into account at all for the Live Demo evolution. The basic procedure will be as follow:

  *   The backlog tracker is https://forge.fi-ware.eu/tracker/?atid=227&group_id=27&func=browse. Please, verify that you have access to the tracker and notify me if in negative case.
  *   We will start by including Epics in the backlog. Each new topic to be included in the Live Demo has to start with a Epic definition.
  *   Then, Epics will be discussed and refined to concrete Features that, in sequence, will be split in User Stories to be developed during the project sprints.
  *   Epics and Features have to be defined in the wiki and trac. For user Stories, it is not necessary.
  *   We will use the "FIWARE.{Type}.Cross.LiveDemo." prefix in our backlog items.

Manuel Escriche, Agile Project Manager in FI-WARE, will ensure that our practices are ok with project methodology. Manuel, don't hesitate to comment on the procedure that I have mention above (or tell us if I'm saying something wrong :)
Two first action points have to be accomplished as soon as possible:

  *   @all: to create Epics corresponding to elements that we want to include in the Live Demo. In this sense, you can have a look to this two examples of elements that (from TID's side) we would like to include.

     *   https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.Epic.Cross.LiveDemo.IoTGEsIntegration
     *   https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.Epic.Cross.LiveDemo.CEPIntegration

  *   @SAP, @TID, @UPM: create Features corresponding to the existing functionality in Live Demo, i.e. Live Demo Release 1, by the partners that were involved in that demo. From TID's side, we will do the part related with our GEs as soon as possible.
We will be using the private wiki and the "FIWARE Private" project in the Forge. A "home page" for Live Demo Evolution has been created at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Live_Demo_Evolution

Don't hesitate to contact me if you have any question on doubt, please.

Best regards,

------
Fermín

PD. The current subscribers list follows. If you miss somebody, please tell me so.

[cid:part7.01070305.01000805 at tid.es]
________________________________

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



_______________________________________________

Fiware-demo mailing list

Fiware-demo at lists.fi-ware.eu<mailto:Fiware-demo at lists.fi-ware.eu>

https://lists.fi-ware.eu/listinfo/fiware-demo

________________________________

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

________________________________

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-data/attachments/20130314/df03ec55/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ATT00001.png
Type: image/png
Size: 20159 bytes
Desc: ATT00001.png
URL: <https://lists.fiware.org/private/old-fiware-data/attachments/20130314/df03ec55/attachment.png>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00004.txt
URL: <https://lists.fiware.org/private/old-fiware-data/attachments/20130314/df03ec55/attachment.txt>