From fermin at tid.es Thu Mar 14 10:39:19 2013 From: fermin at tid.es (=?ISO-8859-1?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Thu, 14 Mar 2013 10:39:19 +0100 Subject: [Fiware-demo] Live Demo evolution kick-off Message-ID: <51419AC7.5040502@tid.es> 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:part4.09080407.03020401 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jddajcjf.png Type: image/png Size: 20159 bytes Desc: not available URL: From fermin at tid.es Thu Mar 14 13:51:37 2013 From: fermin at tid.es (=?ISO-8859-1?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Thu, 14 Mar 2013 13:51:37 +0100 Subject: [Fiware-demo] Live Demo evolution kick-off In-Reply-To: <51419AC7.5040502@tid.es> References: <51419AC7.5040502@tid.es> Message-ID: <5141C7D9.8020209@tid.es> 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 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 20159 bytes Desc: not available URL: From pierangelo.garino at telecomitalia.it Fri Mar 15 08:55:37 2013 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Fri, 15 Mar 2013 08:55:37 +0100 Subject: [Fiware-demo] R: Live Demo evolution kick-off In-Reply-To: <51419AC7.5040502@tid.es> References: <51419AC7.5040502@tid.es> Message-ID: Hi Fermin, I have a question concerning the action point on @All, to better understand the process we're going to adopt: - should we discuss within the team the inclusion of a new topic prior to create the Epic describing it, or - do we act in reverse order, i.e. we first create the Epics as a means to propose additional topics, that later will be discussed and eventually 'approved' for inclusion in the Live Demo? Thanks and BR Pier P.S.: the Live Demo release 1 was not shown at the second year review, but at M18 review. The new version will be shown at the second year review :) Da: fiware-demo-bounces at lists.fi-ware.eu [mailto:fiware-demo-bounces at lists.fi-ware.eu] Per conto di Ferm?n Gal?n M?rquez Inviato: gioved? 14 marzo 2013 10:39 A: fiware-demo at lists.fi-ware.eu Oggetto: [Fiware-demo] Live Demo evolution kick-off 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:image001.png at 01CE215A.DCDD31A0] ________________________________ 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:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 20159 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From fermin at tid.es Fri Mar 15 09:48:38 2013 From: fermin at tid.es (=?ISO-8859-1?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Fri, 15 Mar 2013 09:48:38 +0100 Subject: [Fiware-demo] R: Live Demo evolution kick-off In-Reply-To: References: <51419AC7.5040502@tid.es> Message-ID: <5142E066.7020801@tid.es> Dear Pier, Good written Epics in the wiki provide a description that is very useful for the team to know what is the proposal about and its implications. So, I would suggest doing as you propose as second option: "we first create the Epics as a means to propose additional topics, that later will be discussed and eventually 'approved' for inclusion in the Live Demo" Best regards, ------ Ferm?n PD. You are right, there was a typo in my email. I wanted to mean M18 review :) El 15/03/2013 8:55, Garino Pierangelo escribi?: Hi Fermin, I have a question concerning the action point on @All, to better understand the process we're going to adopt: - should we discuss within the team the inclusion of a new topic prior to create the Epic describing it, or - do we act in reverse order, i.e. we first create the Epics as a means to propose additional topics, that later will be discussed and eventually 'approved' for inclusion in the Live Demo? Thanks and BR Pier P.S.: the Live Demo release 1 was not shown at the second year review, but at M18 review. The new version will be shown at the second year review :) Da: fiware-demo-bounces at lists.fi-ware.eu [mailto:fiware-demo-bounces at lists.fi-ware.eu] Per conto di Ferm?n Gal?n M?rquez Inviato: gioved? 14 marzo 2013 10:39 A: fiware-demo at lists.fi-ware.eu Oggetto: [Fiware-demo] Live Demo evolution kick-off 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. ________________________________ 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. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ 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: From fermin at tid.es Fri Mar 15 16:05:12 2013 From: fermin at tid.es (=?ISO-8859-1?Q?Ferm=EDn_Gal=E1n_M=E1rquez?=) Date: Fri, 15 Mar 2013 16:05:12 +0100 Subject: [Fiware-demo] Live Demo evolution kick-off In-Reply-To: <51419AC7.5040502@tid.es> References: <51419AC7.5040502@tid.es> Message-ID: <514338A8.9030209@tid.es> Hi, I have been asked regarding due dates for this. According to Agile principles, each end of sprint (i.e. end of each month) is a due date itself in which demo functionality gets "frozen". For those dates that we can consider "major" deadlines (such as June review) the idea is to take the Live Demo available in the last end of sprint (in that case, it would be the end of the May sprint). We will follow a strict Agile approach regarding the Live Demo. That means that we will only start the development of any scenario when there are User Stories describing the development. That means that you can propose topics for a new scenario by creating an Epic, but the scenario will not be ready until the Epics have been translated into Features and then the Features into User Stories and, finally, those User Stories have been completed and have led to actual software we can deploy and show running on the FI-WARE Testbed. The bottom line is that the sooner you want to have a scenario supported as part of the live demo, the sooner you have to start working proposing Epics and collaborating in the refinement of those Epics. 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. ________________________________ 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: