Hi all, In this mail I summarize a number of common and specific goals/remarks that WPLs/WPAs should take into account during meetings this week (either individual meetings or joint meetings with other WPs). The meeting room I had allocated for the joint WPLs/WPAs meeting has now been allocated to the Data Chapter from 14:00 until 17:30. However, we will keep the room afterwards, and I will be there to meet any WPL/WPA that may have any doubts about the points below, or want to discuss about any other specific additional topic. Of course, any early feedback you wish to provide over the email is welcome. Now, let me elaborate on the common goals and specific goals: 1. Common Goals: There are a number of points that have to be addressed by all Technical Chapters. Therefore, it is expected that you book specific slots in the agenda of your WP meetings where to address them. I guess that you had already planned most of them but if not, please rearrange the agendas to cope with them. * Architecture Specifications All the teams have to devote the necessary time to push development of the deliverable on Architecture Specifications. This should include sharing/defining the overall structure of the Table of Contents (ToC), and setting up a clear and precise planning regarding development of the defined ToC. I can assume that we won't be able to make the deadline by end of January for this deliverable, but you should develop a planning that secures that the deliverable will be available by February 17, at the latest. * 45m-1h slot to address point regarding needs for the FI-WARE testbed We need to push the task on Testbed design within WP10 and that means that all Technical Chapters have to provide enough information about their needs in terms of physical hardware (number of server nodes, characteristics of hardware for the nodes, connectivity requirements) as well base software infrastructure (operating systems, web/application server technologies, any other base underlying technology, etc.). You should allocate a 45m-1h slot to discuss this in your agenda. Note that all Technical Chapters should provide this info no later than 31st January EOB. THIS IS A MUST. If there is no time to solve this point completely during the proposed timeslot, you should arrange a confcall early next week to close all details. The WP10 team will forward you additional details about the info you have to provide. * Sprint 3 retrospective and Planning of Sprint 4 We should improve the way we are applying Agile in planning of our work. I know this may take some time, overall when not all people are familiar with Agile practices. But it is a matter of persevering. We may have not make it that well during the first three sprints, but is time to try it hard from now on. In this respect, I ask all of you to book the necessary time slots in the agenda to carry out the following two meetings, which from now on you should plan in subsequent sprints: Sprint 3 retrosprective: within this meeting, you should ask members of your teams two basic questions: a) What went well during the Sprint ? (this particularly includes report on what got finalized as planned) and b) What could be improved for the next sprint ?. Answer to the second question should lead to a set of actionable items, some of which should be planned as WorkItems in the next Sprint. Planning of Sprint 4: Take the opportunity to use this f2f meeting to plan items to be addressed in Sprint 4. Bear on mind that it maybe a good idea to map some Action Points you will identify during the meeting into WorkItems to be addressed within Sprint 4. * Revision of Features for second minor release of FI-WARE and development of Technical Roadmap You should be able to identify the Features that will be part of your respective backlogs. You should also identify which of them will be addressed in the second minor release of FI-WARE (Sprints 4 to 6). Adding Features that were already identified (and supposedly addressed) in the first minor release (Sprints 1 to 3) and Features planned for the second minor release should lead to definition of Features that will be supported by the GEs in the first mayor release of FI-WARE, to be made available through the FI-WARE Testbed. You should allocate some timeslot during this week to come up with a plan to get the final set of Features, linked to each of the GEs in your chapter, that will be supported in the first major release of FI-WARE. The Technical Roadmap deliverable that was due by end of January (which probably has to be delayed until Feb 17) will be based on this list of Features linked to the first major release of FI-WARE plus a set of high-level Epics you envision that will be addressed in subsequent major releases. * Standardization Plan All chapter teams have been asked to provide detailed info about the standardization activities/plans, including description of relevant bodies you plan to address. Please allocate a time slot during your meeting to collect this info and send it to NEC (leading this task) in the proper format. NEC had already sent to you a request for information about this matter, so please refer to it. * Preparation of month 12 deliverable: RESTful operational interfaces Bear on mind that month 12 deliverable should include a detailed specification of the APIs that GEs in your chapter should support. In order to provide an homogeneous set of APIs, based on what could be a common denominator, we should go for specifying them following a RESTful approach. Please take the necessary time to communicate this to owners of GEs. Specification and implementation of RESTful interfaces may require identification of features to be included in the backlog and probably identification of work-items or user stories in Sprint 4. * USDL specification of business-related aspects of interfaces We should support scenarios where most of the FI-WARE GEs in FI-WARE (particularly those in the IoT, Data/Context and Apps Chapters) provide their functionality "as a Service". This will allow that applications deployed on a FI-WARE Instance be able to use them and pay for their effective use (e.g., an application would pay for use of the NGSI Publish/Subscribe GE, based on number of events consumed or any other parameter). This will require that the business-related/monetization aspects of GEs be specified using USDL. A presentation about the implications of using USDL will be made on the plenary session on Wednesday by SAP (Torsten) and Chapter teams are requested to devote some time slot during their meetings on Thursday/Friday to discuss and plan how they can support what is needed for delivering their functions "as a Service" and charging for using them. * Discussion on how to use the Identity Management and Access Control GEs provided by the Security Chapter Identity Management and Access Control are going to be key GEs in FI-WARE that will interface with most of the GEs in FI-WARE. All GEs must indeed be able to rely on Identity Management and Access Control APIs/functions to implement part of their behaviour. A presentation on the architecture of the Identity Management and Access Control GEs as well as the APIs they will provide will be made on the plenary session on Wednesday by Thales (Pascal). Chapter teams are requested to devote some time slot during their meetings on Thursday/Friday to discuss and plan how they will integrate with these core Security GEs. * Revision of UC projects' tickets During the FI-PPP AB meeting celebrated on Jan 19-20, several UC projects have complain that they haven't seen any progress regarding handling of their tickets. There was a push, matching the review we had in late November but things seem to be stopped now. You should allocate a time slot for this in your agendas. Technical Chapters (WPs) are requested to report on all these points above as well as all other points addressed during their meetings by means of elaborating comprehensive minutes. To ease development of the meeting minutes, we suggest that you develop them on Google Docs. I have experienced this technique in a number of recent meetings and the results are surprisingly good. To achieve the best results, you should share your minutes in Google Docs with the rest of your team while at the meeting. This will be extremely useful because this will allow all of them to help you capturing everything that is relevant (many times, they will help you just because they are the first that are interested in that something that affects them is accurately captured :-). This will lead to elaboration of rather complete minutes which, in turn, will be revised and approved by all partners of your team much faster. This will also allow you to share the minutes with me while the meeting progresses so that I can get aware on what's going on every day. Later this evening, I will forward the links for the Google Docs where you should write down the minutes. I will prepare them so that they have a common template (which will be aligned with the one we have proposed so far for the project). 2. Specific Goals: Besides the aforementioned common goals, there are a number of specific goals that I wouldn't like the involved chapters to forget. Here you have a summary of them: * Definition of Epics for BM&BE topic in 1st Open Call The Apps Chapter has to plan how to derive the set of Epics that have to do with the BM&BE topic that will be part of the 1st Open Call in FI-WARE. Note that the more concrete you are, the better so that submitters can propose technology that may fulfill the current gap in the Business Framework Reference Architecture. This is a task that requires SAP full attention, as leader of the WP. * IoT and Data Chapter should reach final agreement on approach regarding NGSI and CEP We have to close an agreement about the role of NGSI will play in the IoT target architecture, what level of compliance with current OMA specs we should achieve because it makes sense to. Besides, we should agree who implements what to make sure that unnecessary duplication of efforts is avoided. We also should agree on what approach to adopt regarding CEP. * I2ND and Cloud Chapter should agree on how I2ND interfaces could be exploited by Cloud Hosting GEs I2ND and Cloud chapters should try to come with a sketch on how Cloud Hosting GEs may rely on I2ND interfaces to guarantee those SLOs that will rely on end-to-end communication QoS parameters. Note that these are not the only specific goals to be covered during this f2f meeting. I haven't elaborated on the specific goals that each of the chapters has. 3. General remarks: * Each Action Point (AP) identified during the meeting that implies a non-trivial work should lead to a WorkItem in the respective backlog. Cross-WP APs to be included in the FI-WARE Private Backlog that will be setup during today. -- 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20120122/7224a6ff/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy