FYI. I hope that the reviewers and our PO will value the great effort made and also the attempt to generate pretty-printable versions of this deliverable. Definitively, I believe that rejection of the FI-WARE Technical Roadmap deliverable should be solved. Let's focus now on the FI-WARE Architecture Description and the Open Specifications. Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es<http://www.tid.es> email: jhierro at tid.es<mailto:jhierro at tid.es> twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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 -------- Original Message -------- Subject: Re-Submission of deliverable D2.4.1 FI-WARE Technical Roadmap Date: Thu, 06 Sep 2012 18:51:19 +0200 From: Juanjo Hierro <jhierro at tid.es><mailto:jhierro at tid.es> To: Arian.ZWEGERS at ec.europa.eu<mailto:Arian.ZWEGERS at ec.europa.eu> <Arian.ZWEGERS at ec.europa.eu><mailto:Arian.ZWEGERS at ec.europa.eu>, dgr at whitestein.com<mailto:dgr at whitestein.com> <dgr at whitestein.com><mailto:dgr at whitestein.com>, msli at icfocus.co.uk<mailto:msli at icfocus.co.uk> <msli at icfocus.co.uk><mailto:msli at icfocus.co.uk>, renaud.difrancesco at eu.sony.com<mailto:renaud.difrancesco at eu.sony.com>, irena.pavlova at isoft-technology.com<mailto:irena.pavlova at isoft-technology.com> CC: Miguel Carrillo <mcp at tid.es><mailto:mcp at tid.es>, Jose Jimenez <jimenez at tid.es><mailto:jimenez at tid.es>, "jhierro >> \"Juan J. Hierro\"" <jhierro at tid.es><mailto:jhierro at tid.es> Dear Arian, dear reviewers, This is the official submission of the following deliverable: * D2.4.1 FI-WARE Technical Roadmap The deliverable is publicly available in .pdf and .docx format: * .docx format: https://forge.fi-ware.eu/docman/view.php/7/1287/D2.4.a+FI-WARE+Technical+Roadmap+resubmission.docx * .pdf format: https://forge.fi-ware.eu/docman/view.php/7/1288/D2.4.a+FI-WARE+Technical+Roadmap+resubmission.pdf The .docx version is provided because it would allow you to navigate to the FI-WARE FusionForge from the document. This will allow you to see the description of a given Feature of a FI-WARE GE, for example. Unfortunately, we haven't been able to generate the .pdf file with links. The deliverable is, of course, available on the FI-WARE wiki and keep there constantly updated for reference. Availability of the FI-WARE Technical Roadmap was announced to the UC projects on August 29th (during the virtual meeting of the FI-PPP AB planned that date) but we haven't been able to generate the .docx and .pdf files until now. Please note that .docx or .pdf versions of the FI-WARE Technical Roadmap are pure snapshots of what is published on the FI-WARE wiki, which is the ultimate valid reference. Following is an explanation on how we believe that the re-submitted deliverable addresses the comments that were made during the review in month 9: * The re-submitted version of the deliverable incorporate tables that clearly specify what Epics/Features will be covered in each Release by each of the FI-WARE GEs. Mapping between Releases and Epics/Features defined in the FI-WARE Backlog has been documented in detail for this purpose. By reviewing the description of each Epic/Feature in the Backlog, a potential reader will get enough details about what will be offered by each FI-WARE GE when. This in contrast with the original submission of the deliverable where functionalities/features supported were described in a very high-level. * The provided description of Epics/Features is enough detailed in our opinion and it should allow the Use Case projects to understand the FI-WARE propositions correctly, avoiding wrong expectations and further difficulties in the collaboration. * Several topics have been identified during interaction with UC projects that were not planned in FI-WARE. Those topics are being addressed through the 1st and 2nd Open Call so far. Following an Agile methodology, Epics have been defined for each of those topics. However, no partners have yet joined FI-WARE as a result of the 1st Open Call, so it is still too premature to specify what features linked to topics of the 1st Open Call will be delivered by what FI-WARE GE and when. Current plans are that submitters of winning proposals to the 1st Open Call will join beginning of October 2012. Detailed planning of Features to be developed will not be incorporated into the Technical Roadmap until release D.2.4.2 by end of January 2013. Nevertheless, Deliverable D.2.4.1 comprises references to the Epics linked to topics in the 1st Open Call since they will be subject to analysis and target for development in the 2nd release. * We definitively believe that this Technical Roadmap indicates the delivery schedule for precise Generic Enablers, which have been described in terms of the whole set of features they will provide. * A finer grained estimate of the delivery date for each feature and FI-WARE GE is provided compared to the original submission of the deliverable, but to the extend it is possible taken into account that we are following an Agile approach. We kindly remind that planning what are going to be the features covered in all releases projected in the future at this point would go against Agile as methodology. In summary, we believe that this deliverable brings information about the FI-WARE Technical Roadmap that goes well beyond the amount of information that is typically published by any Platform provider when it publicly announces its roadmap/plan to the market. As per today, UC projects has not yet started to use the FI-WARE GEs on the FI-WARE Testbed. We expect this will bring the opportunity to capture detailed requirements about functionality they will require that in turn will map into Epics/Features to be incorporated in each FI-WARE GE Backlog. However, this process has not started yet. So far, UC projects have been only able to provide very high-level requirements with respect to FI-WARE GEs under development and those requirements neither contradicted nor added functionality that is described in the currently identified set of Epics/Features. We would like to remind that functionality that is not enough detailed cannot be given any priority according to the Agile methodology. Therefore, asking for prioritization of requirements from UC projects is premature at this time. Nevertheless, we are working with them so that they can list themselves as stakeholders of specific Epics/Features and this may help us to prioritize development during the second Release of FI-WARE. They have been requested to do so by means of editing the "stakeholders" field of Epics/Features in the FI-WARE Backlog. Should you have any comments or suggestions, do not hesitate to contact us. Kind regards, -- Juanjo Hierro ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es<http://www.tid.es> email: jhierro at tid.es<mailto:jhierro at tid.es> twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: 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/fiware-wpa/attachments/20120906/386fbd77/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy