Dear Partners, Find below retrospective from Sprint 6.2.1 (January-17). The issue holding the content is https://jira.fiware.org/browse/COR-889 The summary that I can get from this report is a light going down of activities during last sprint. Maybe the problem was the transition period between FI-Core and FI-Next project. I hope that it should be recovered during the Sprint 6.2.2. Last but not least, some chapters are not provided their retrospective. I do not know how was it defined previously but I would like from now on to send the Retrospective of previous Sprint the same day that I send the Sprint Planning for the current Sprint. ----------------------------------------------- WHAT WENT WELL ACHIEVEMENT FEELING. Lab * No planning for the sprint. Apps * A new version of the BusinessAPIEcosystem has been released. * Created a initial prototype of CKAN-NGSI-WireCloud integration using the Air Quality data models. Cloud * Nothing reported. IoT * Nothing reported. Data * Most sprint tasks for Orion and Big Data analysis were completed as planned, by end of the sprint. * Asynchronous inputs to the meeting minutes and to the WPL has proved to be an effective way of working. I2ND * Nothing reported. WebUI * No particular events to report. Ops * No planning for the sprint. Academy * No content to report. Catalogue * No content to report. Security * No more items worked out except from IdM GE (i.e. Keyrock). * This shows that GEs are now mature and stable enough. WHAT TO IMPROVE: BLOCKADE/RISK FEELING GOALS/TARGETS/OBJECTIVES Lab * No planning for the sprint. Apps * WorkItem on SmartCity Demo cannot be processed because of lack of information. Cloud * Nothing reported. IoT * Nothing reported. Data * The current backlog management policy based on excessive control mechanisms and micro-management, is a severe burden for development teams. * Kurento GE owner should provide asap their sprint backlog, following the items agreed during the FIWARE Summit and in the weekly chapter calls. I2ND * Nothing reported. WebUI * Creation of road map pending, also depending on planned content in FI-NEXT Task 3.1 and 3.2 . Chapter internal roadmap, including partners not covered by funding from FI-NEXT, is planned to be created by end of Sprint 6.2.2. Ops * No planning for the sprint. Academy * No content to report. Catalogue * No content to report. Security * Nothing reported. Thanks for effort, contributions and cooperation!! Kind regards, Fernando -- Fernando López FIWARE Scrum Master Franklinstrasse 13A 10587 Berlin - Germany fernando.lopez at fiware.org www.fiware.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware/attachments/20170213/9e9ff522/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy