Dear Partners, please find below a mail from Juanjo, concerning the future actions in FI-WARE, which imply obviously also our contribution, along with some comments on the preparation of a f2f meeting the WPA/WPLs have the next week in Rome. You'll see that, as I already mentioned to most of you, the architecture update is formally postponed of a couple of months, to let us incorporate the changes which might come up by the chapter revisions going on in this period, and by the further outcomes of the f2f meeting. The analysis of the topics/items listed in this mail will be the major point in our periodic PhC on Thursday, with consequent definition of main actions on our side to support the project actions. I provisionally add, as proposed agenda for the PhC, the following topics: - Revision of GE architecture - Status of I2ND white paper (just to be clear: the our internal 'white paper' for which first contributions should come tomorrow; no relationship with updated of product vision) Please feel free to add other topics that you consider worth to be addressed in our call. BR Pier Da: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] Per conto di Juanjo Hierro Inviato: venerdì 11 gennaio 2013 17:37 A: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Oggetto: [Fiware-wpl] Next steps: what we should be focus on during January Hi all, I'll try to summarize in writing what I explained in the last joint WPLs/WPAs follow-up confcall regarding what to do next. Hopefully, that way the message gets more clear. Nevertheless, I'll capture the contents also in the minutes so that everyone have this in front of him at the next call. Our focus during the first half of this year should be delivery of the 2nd Release of FI-WARE by end of July, so that we are able to launch the FI-WARE Open Innovation Lab at that time without delays. In order to make the 2nd Release a success we need to deliver software that not only works but bring the necessary functionality to be attractive, useful and usable enough. For that reason, my intention is that we close end of January with a clear vision of the functionality that we will try to cover during development of Release 2 of FI-WARE. And the exercise we have to focus on during January has to do with trying to document the functionality we are aiming to cover in the form of Themes/Epics/Features. We are now at the beginning of a minor release (2.2, see [1]). Therefore: * Features in the backlog of your chapter should match concrete functionality that a given GE in your chapter will provide, which we can COMMIT will be developed in just 3 months during the current minor release (which ends by the end of March) or the next (which starts beginning of April and ends by end of June) * Epics in the backlog of your chapter may be related to functionality we want to see in a given GE but we will need to further analyze until it becomes a Feature (i.e., we reached a point at which we can COMMIT in what minor release will be planned) * Epics may also relate to cross topics that we all agree have to be covered (e.g., how OAuth is going to be adopted in all APIs in a non-intrusive manner). They will evolve from Epics registered in a general FI-WARE backlog tracker (that I'll setup in the FI-WARE private FusionForge project) and we will evolve them through joint discussion until they become Epics at chapter level and then chapter partners shouldn't stop their refinement until they transform into features of GEs (all the existing ones, just some of them, or a new GE) * We can have some Themes as well, mainly to pencil topics we shouldn't forget to deal with at some later stage (note: totally aside of this mail but something I believe is worth reminding: we agreed that user stories are not longer required to be documented in the public wiki. We will just keep tickets in the tracker when we reach the level of user stories or work items) The exercise we will concentrate on during January is that of generating a complete and updated version of the backlog. Once we have it ready, we'll be able to quickly generate two of the deliverables that were due by end of January: * FI-WARE Technical Roadmap * FI-WARE Backlog Then, a first draft of the FI-WARE Architecture Deliverable linked to Release 2 of FI-WARE be ready by end of February, and from then, carry out a number of peer reviews until official delivery by end of March. Very much important, is that also from end of January on we will follow an Agile approach where planning of Sprints and results of those Sprints will be followed-up rigurously. That way we will be able to prevent that we discover, just in the last minute, i.e. June, that we are not able to deliver what we promised. Each Sprint focused on a) further refining Themes/Epics/Features and b) executing selected user stories and work items Note that the exercise of completing the backlog, and further refining the Epics, should naturally come along with discussion about how to solve some technical issues from an architectural point of view. And that is the kind of input that is necessary to develop the FI-WARE Architecture document. My intention, therefore is that we don't start introducing changes in the FI-WARE Architecture until things have been properly discussed. Given said all the above, every WPA should attend the f2f WPAs/WPLs meeting in Rome with a presentation of Epics they believe require a joint discussion. Also of course with an elaboration on his vision on the matter. If you can even anticipate them ahead of the meeting, the better. Indeed, this is the exercise I asked you to carry out before Christmas, which should be documented in [2]. It would be worth that you take a look at the existing Epics before adding new ones. In some cases you may find that the topic you want to address matches an existing one. In such a case, please try to add to the description whatever thoughts you have on the matter. This is the must-do homework every WPA have to prepare for the f2f in Rome. Of course you can leverage on input from your respective teams so that I suggest you share with them this exercise. Indeed, I rather suggest that you share this mail with your teams. More homework regarding the f2f meeting will come along the agenda of the meeting that I already anticipated I will send to you along this weekend. [1] - http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates [2] - https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Global_Epics 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 ________________________________ 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: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20130114/453a5532/attachment.html> -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20130114/453a5532/attachment.txt> -------------- 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: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20130114/453a5532/attachment.jpg>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy