Dear Partners, Please, find below the global retrospective for Sprint 5.2.3 You can also access it at the corresponding jira issue: https://jira.fiware.org/browse/COR-812 Global Retrospective for Sprint 5.2.3 WHAT WENT WELL ACHIEVEMENT FEELING. Coaches * All - or most of - the normal coaching activities were handled without any particular problem, including Community Account registration and incoming general and technical requests from Startups/SMEs (CEED-Tech, IMPACT, CreatiFi, FI-ADOPT, FRACTALS, FInish, SmartAgriFood). * The review of the technical assessments and the webinars planning were performed (CEED-Tech). * The fiware-training-req channel seems to work now (CEED-Tech). * No activities in Sprint 5.2.3 for SpeedUP accelerator (SpeedUP! Europe). * The new modifications introduced by Manuel in JIRA regarding comments and emails are appreciated by the coach for INCENSe (INCENSe). * The evaluation of the technical documentation has been carried out (CreatiFI). * The acceleration program in FICHe is reaching its end (June 2016) and no requests were received (this comment was provided during the Coaches Closure meeting; see the related minutes) (FICHe). * Training days were interesting to acknowledge the most frequently detected issues (by sub-granted) related to configuration, interoperability, installation, and services connection of the various GEs (FINODEX). * Budapest and PiraeusU FIWARE Lab node Teams were very helpful and proactive during the migration of Startups/SMEs from shutdown nodes to new ones; the former was helpful also for HELC tickets (FI-ADOPT, FRACTALS, FInish, SmartAgriFood). * For the FI-C3 accelerator, about 15 requests were handled in relation with overall deployment of GEs (i.e. KeyRock/IDM, Object Storage, Cygnus & Context Broker, POI, FIWARE Lab); most of them were handled locally at EGM and some of them did request support from the GE owners (i.e. POI, KeyRock), who did provide support swiftly (FI-C3). * A face-to-face technical review meeting has been planned for April, supporting around 40 FI-C3's Startups/SMEs (FI-C3). * The evaluation for the FABulous' Startups/SMEs made by the related coach (Pasquale) has been a profitable chance to understand the accelerated projects; the methodology for evaluation included a public spreadsheet with the list of projects and the list of the enablers, and all the Startups/SMEs have filled their own line (selecting the proper sub-list of enablers), then Pasquale checked the various projects and performed a double-check of the results, contacting the Startups/SMEs in case of problems (e.g. differences in the final result); only two Startups/SMEs did not complete the public spreadsheet (FABulous). Collaboration * The experience in using JIRA has been useful to change a bit the structure of tasks. It is much easier now to understand the big elements of collaboration activities and report the tasks for the benefits of the consortium. Components are more rational now even though the overall content is more or less the same * Some of the partners replied more proactively this time in terms of reporting their activities in this sprint. This leads us to think that they are getting used to do it and collaboration WG will benefit from this discipline * Good achievements especially in the area of collaboration with FIWARE Mundus. positive results from the activities in US and good prospects in Brazil, even though this region has more uncertainties Dissemination * Meeting point with the EC to start planning transition to FIWARE Foundation. * Finally clarified support to CampusParty Events. *Closed collaboration with TM Forum (both Challenge and event sponsorship). Exploitation * Start to gather some market analysis about IoT Platforms, Smart Cities, Smart Industry, and Industry 4.0 * Recompilation of all the commercial initiatives by the CORE Group in the monthly meetings * A FIWARE Business global workshop organized by Atos Iberia for the whole Atos Group, in April Press Office * Day to day operations smoothly running. No barriers. * No issues with website operation and content. * Little production in this sprint. No delays. Apps * Most of the issues has been closed * There is a new release of WireCloud with the progress of Release 5.2 Cloud * Help desk support good and timely. * Team is working well together (example Cloud Portal support of Murano) Data * Almost all planned items in the sprint were completed on time. * Generally, help desk issues have been well attended by the corresponding GE owners. Security * Progress as planned on IdM & PEP GEs * FIWARE Startupyard meeting for coaching PDP GE users WebUI * Completion of Github-tasks (badges etc... ) well explained, so finishing them took only little amount of time * Integrating secure communication into POI Data Provider succeeded well Ops: * Good progress in all the tasks of the chapter * Relevant improvements in Monitoring where the integration of the new architecture has been finally deployed (at least for the Spanish node) Academy: * The activities for the new theme are in a good stage. First beta version is planned to be ready by early April and it will be sent to Ogilvy for validation and comments Catalogue * The Chapter Leaders Role functionality has been completely finished. Some possible improvements has been identified, to be worked on in the next months WHAT TO IMPROVE: BLOCKADE/RISK FEELING GOALS/TARGETS/OBJECTIVES * APPS - Wirecloud was not able to finish the support for changing the colours of the theme when embedding dashboards * APPS - Some of the work carried out for BusinessAPIEcosystem was not initially reflected in the backlog * CLOUD - Architecture deliverable is taking too long. * DATA - Stability issues related to Proton CEP and the usability of its Docker image still need to continue being worked on. * DATA - Due to an increase in the number of CKAN related help/support requests during this sprint, some of them could not be attended for several days. The internal process for help desk management in OKF needs to be improved. * SECURITY - Documentation should follow development * SECURITY - REST service framework used by the PDP GEri * OPS - still some development activities, mainly related with monitoring and synchronization, not totally completed as planned * CATALOGUE - Aspects to improve: The TextUnderDownloadTab functionality has taken more time and effort than initially expected. The initial approach to implementation (redesign completely the pages) has not been finally practically possible and a more simple implementation has been finally adopted (add an additional explanation field in each link) * PRESS OFFICE - Planification of related events to materials, especially booth production: To close to event, risky approach. * DISSEMINATION - FIWARE role and presence at NetFutures still not 100% clear. Booth design at risk. * DISSEMINATION - Lack of Dissemination Plan and related event long term, checking available budget till project end. LAB * CLOUD - Storlets are still not deployed FIWARE Spain. * COACHES - The migration from shutdown nodes were not handled in a proper way by some of the FIWARE Lab teams and the following list contains the faced problems and issues (FI-ADOPT, FRACTALS, FInish, SmartAgriFood): * COACHES - some Startups/SMEs were left without VMs access for weeks; * COACHES - the PiraeusU FIWARE Lab node experiences some hard disks space issues, so despite the helpfulness and the proactivity of the node Team, the migration for some Startups/SMEs was not completed; except for Budapest FIWARE Lab node, other nodes did not volunteer to help; HELP DESK/SUPPORT * WEBUI - KeyRock documentation for non-Node.js users is not very extensive e.g. compared to documentation of Google+ authentication e.g. * COACHES - Two tickets related with potential problems in GEs are still open (CreatiFI). * COACHES - It is still difficult to know the solutions to all possible problems related to the GEs (FINODEX). * COACHES - The support for SEs is not provided anymore and this is starting to create some issues for the Startups/SMEs (FI-ADOPT, FRACTALS, FInish, SmartAgriFood). TEAM: COMMUNICATION/RESPONSIVENESS/COMMITMENT * Scrum Master - * IOT - No contribution to retrospective * Sustainability - no way to hold agile (planning and closing) meetings for several sprints * COACHING - No feedback provided by the coaches from the following accelerators: EuropeanPionners, SOUL-FI, FrontierCities. * DATA - CKAN has improved in terms of conformance to FIWARE Agile dynamics rules and guidelines, however this still needs to continue being worked on. * WEBUI - Owners of FIWARE Lab community accounts were not made aware of that the account expires at a certain date. This caused some impediment in maintaining / developing public instances. Would be good to have non-expiring account for us involved with FIWARE, or at least a warning e-mail before expiration. * WEBUI - Short notice of changes needed in documentation delayed planned design work. * COLLABORATION - Not all the activities have been reported, but this sprint was close to the deadline of the ICT call, where many FIWARE partners are working, also in collaboration with other organizations (such as OASC for the domain of smart cities). This may have had an impact, but should not influence the next sprint * EXPLOITATION - More collaboration from the rest of the partners in gathering market analysis and in providing strategic guidelines * COACHING - Still no info about how to proceed with the FIWARE VIP program regarding the new selected Startups/SMEs (Stefano will contact Angeles and Juanjo about getting direction for this; see the related minutes) (CEED-Tech). * COACHING - The new selected CEED Tech's Startups/SMEs seems not included in the FIWARE Community group on Mobilize platform (Marco, the related coach, will contact Angeles Tejado and ask to include these new teams in the group) (CEED-Tech). * COACHING - the FIWARE Lab node Teams do not know exactly the process to follow for the VMs migration and in some cases they just asked for a new apply for a Community Account to Startups/SMEs in a different FIWARE Lab node; * COACHING - A closer follow-up from the FIWARE Lab coordination team on the nodes and a clear assignment of responsibilities are needed in order to improve future migrations or similar tasks. * COACHING - some FIWARE Lab nodes refused to help with the VMs migration phase, claiming they are not funded (e.g. Prague); * COACHING - some nodes refused to offer the availability for VMs migration even though they were funded (e.g. Spain); eventually they helped the Startups/SMEs only for a particular case, but stated they can't do it for other cases; * COACHING - in one case, wrong VMs were migrated (VMs belonging to other Startups/SMEs); * COACHING - because of this FIWARE Lab nodes' behaviour, some of the involved Startups/SMEs decided to leave FIWARE Lab and, worst situation, some of them missed their deadlines for making demos due to not timely completed migration; * COACHING - Some GE owners are not very responsive to incoming training requests (FI-ADOPT, FRACTALS, FInish, SmartAgriFood). Thanks for effort, contributions and collaboration. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader IOT Innovation - FIWARE Initiative Telefónica Digital Parque Tecnológico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34. 983.36.75.13 http://www.tid.es<http://www.tid.es/> ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware/attachments/20160422/c9da1638/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy