Dear All, In our last confcall we defined a number of actions to be performed, some are urgent!, so let me try and explain how to progress more rapidly, according to the clarifications I got from the periodic call I had with Juanjo and Thomas on Friday (maybe with some simplification that I hope doesn't create other concerns and/or doubts), and define what is practically expected to be done by all of us. 1. The Product Vision is what we are going to implement in FI-WARE, split into each FI-WARE Chapter: this is of course our GEs (so our final products!), and this description details the functionality we want to provide for each of them, and their interfacing. The Product Vision is described by the Fi-WARE Wiki page(s) at URL https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Product_Vision and is 'automatically' translated from the High Level Description (D2.2a) document. 2. Portions of the Product Vision functionality may have been already available, through the Assets each partner is contributing to the project. There will be a place where the assets will be described in the Wiki pages (associated to the Product Vision). For the time being the guidelines to insert the asset descriptions are not yet available. As soon as available I'll tell you how they need to be uploaded; for sure they will derive from the asset descriptions we have already produced or we are (still) producing now. *So please do strictly comply with the rules for asset description we established in our I2ND confcall last week, and provide them urgently (see Action Points from I2ND40 to I2ND42)*. 3. There are further functionalities of our GEs which are not yet available/implemented (e.g. no asset available for them), but they need to be provided to complete the expected functionality of the GE: these are the 'things to do'. We have to 'capture' them through the EPICs descriptions we started to generate in past weeks and insert them in the FI-WARE Backlog (see point 4 below). *This is our main work concerning EPICS to be done right now (see Action Points I2ND43-I2ND45)!* Some more details: o An EPIC should represent mostly work to be done (i.e. developments in the project's lifetime). They can however represent a mix of available functionalities (already available through the assets) and new functionalities. o An EPIC representing more than 75-80% of an assets functionality is not considered an EPIC for FI-WARE; we should therefore try and focus the EPIC on the 'missing' parts. A consistent Chapter EPIC should represent max 25% of available functionality and the remaining description should refer to 'work to be done'. o More clarifications about the EPIC contents and their difference with respect to Features/User Stories can be found in the attached mail (it was a request by one Chapter member to Juanjo for clarifications) and in the Wiki page https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Agile_Development_Methodology . Remember that the 'hierarchy' is Themes/EPICs/Feature/User Stories. 'Feature' entry is new, and sits in between EPICs and User Stories; it was introduced to provide Use Case Projects more detailed capabilities. o One further rule of thumb: EPICs have to be useful to us that will have to implement the functionality required, remember this when describing them... 4. Once the EPICs comply with the rules explained above, we have to enter them in the FI-WARE Backlog, here is how to do it (this is answer to Action Point I2ND44): o Read carefully the tutorial at Wiki page https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_add_the_full_description_of_backlog_entries_to_the_Wiki I believe the explanation is rather clear, and it should not create troubles. o The https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Backlog WIki page contains already some EPICs introduced by other Chapters, you can see how the final result of your insertion should look like. o Please agree with the Task Leader the insertion of the EPICs in the FI-WARE backlog. *We have to urgently target the insertion of the Primary EPICs we defined in our last confcall*. TLs should in turn talk to Hans and me for coordination of this process (and for any further doubt about EPICs insertion). o At a later stage the FI-WARE Backlog entries will be associated to entries in the FI-WARE Tracker (more info on this step asap). Sorry if this mail is rather long, I hope however it can dissipate some of the doubts you might still have about the actions we need to do. For further clarifications please share with all of us the issues you might identify. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 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:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20111003/6df02d20/attachment.html> -------------- next part -------------- An embedded message was scrubbed... From: Juanjo Hierro <jhierro at tid.es> Subject: Re: [Fiware-wpl] FI-WARE - Urgent - delivrables to provide for tomorrow - request for clarification Date: Thu, 29 Sep 2011 19:39:22 +0200 Size: 33860 URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20111003/6df02d20/attachment.mht> -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20111003/6df02d20/attachment.jpg>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy