Dear Partners, Find below the global retrospective from Sprint 4.4.3 corresponding to the input received in September. Find Retrospective in JIRA issue<https://jira.fiware.org/browse/COR-439?focusedCommentId=35006&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-35006> IOT and Security chapter leaders didn't provide due retrospective. Global Retrospective for Sprint 4.4.3 WHAT WENT WELL ACHIEVEMENT FEELING Apps * The release is complete and all the deliverables have been delivered; * We were able to close all the foreseen activities; * We were able to follow the provided guidelines; * According to us, the chosen tools (Docker, RDT, ...) are appropriate; * All the work items and deliverables assigned to this sprint for the release 4 has been completed/delivered. Cloud * We completed all relevant items WebUI * Task which were not impeded processed smoothly Ops: * Finalised the deliverable D.21.1.1 following the guidelines * The overall percentage of completion is above 90% Academy: * This sprint is mostly dedicated to create the deliverables User Guide and SW Release for the FIWARE Academy. Part of the work was dedicated to review the new or updated courses and support GEi owners in that operation. Catalogue * Significant advances have been made in complex issues related to the Catalogue architecture (e.g. LDAP integration) * The basic software related to the implementation of the search side bar functionality have been completed * The wiki section related to the use of the Catalogue by standard users have been updated (feedback by the users seems clearly positive) * Google analytics has been integrated in the development platform of the Catalogue TEAM: COMMUNICATION/MEETINGS * OPS - Madrid face-to-face meeting was very helpful to refocus priority and have a wider view of the WP and for the future planning OTHERS * DATA - Centralization of help desk issues from stackoverflow to JIRA * I2ND - R4 very well managed by WP Coordinator * CLD - In General Docker was very simple to use and worked well. Installing Docker was easy WHAT TO IMPROVE: BLOCKADE/RISK FEELING GUIDELINES * DATA - Guidelines provided in the automatically added Jira items were not clear and precise enough: readthedocs, apiary, docker.. Some were not even correct (e.g: asking to generate pdf and upload to Github) and resulted in excessive effort for GE owners to resolve these items. GOALS/TARGETS/OBJECTIVES * CLD - There were a lot of items to deal with since it also was the release completion. Next release cycle should give more time and fore thought ending the release more smoothly.* * WEB - It should be noted that due to the vacation of both Philipp and Torsten during this Sprint some coordination tasks could not be completed in time. We trying to catch up once we are back up to full attendance next week. * ACA - From the next sprint we have to give priority to the new theme for the platform * DATA - Many work items were added automatically to Jira without a previous discussion about them (some even in the middle of the sprint) and delayed resolution of other planned items. * OPS - Still some difficulties in FI-Toolkit to address all the tasks planned TOOLS: * APPS - tools for the release (apiary pdf generator, etc..) were not provided in time; * APPS - the pdf and the site generated by the provided tool for parsing the apiary spec is horrible (ugly style and poor usability). * CLD - Still need direction on how to convert the apiary to the html format. * DATA -Karma metrics measurement per GE is opaque and comes after sprint closure, therefore not really giving the option to solve the issues during the sprint itself. * I2ND - The extensive use of new tool such as Apiary, readmydocs, docker has increased the needed time in order to complete the tasks (at least for the first time). Some development did not fully comply with open specs (firos component in robotics GE) * WEBUI - Tools for data converting from apiary to html were provided way too late considering given deadline * WEBUI - Some new things, especially Readthedocs and Docker, have caused more work than anticipated. So many other works are delayed. * APPS- I do not have the tickets to create the cloud image and update the academy course. However, I think that they are required even tough the founding for this GE has been stopped for the NEXT release. Academy Course & Cloud Image are required deliverables for Release 4, so we need to deliver it to get all the founding of THIS release; DOCUMENTATION * APPS - FIWARE documentation is dispersive (something in the Wiki, RDT, GitHub), i.e. it not centralized; * APPS - for some tasks, documentation in particular, it should be better if we could automate them, instead of depending on a human interaction; TIMING: * WEB : It's hard to get documentation ready within the deadline when the tools and guidelines are send one day before the deadline or after it (Apiary to pdf converter). OTHERS: * APPS - there were a lot of technical questions this spring due to the accelerate programmes ending this month. It's hard to answer those questions while trying to make the final release; * CAT - The integration with LPAD continue to need some clarifications/decisions related to the design * OPS - VM hosting SLA Manager disappeared from FIWARE Lab. The reason is still unknown. This has a certain impact on the activity of FI-Dash and must be investigated deeply. TEAM: COMMUNICATION/RESPONSIVENESS/COMMITMENT * CAT - The workflow involving O´Gilvy has some negative consequences given the (too high sometimes) delay in getting an answer from them. Perhaps there is a need for not waiting for the O'Gilvy response (at least for fairly basic design changes) Let me some comments: Yes closing R4 has indeed been a complex process for several factors: - Strategic decisions taken at highest level, with its contract redefinition (amendment) - New tools and procedures to make FIWARE Open to the Community - Setting targets to close the release for ALL Tech partners - Being Summer time, which prevents right communication and awareness >From the coordination team a great effort has been done to get everything aligned in time. - Global work items were created which carried guidelines to every single GE owner. - Each global work item had its own caretaker to answer related questions about the guideline. - Each global work item had its corresponding description (link to guideline), its deadline and caretaker declared as watcher This was explained during the sprint planning in all chapters, therefore some comment received are from people not attending them. The whole process was a challenge: although tools had been used previously successfully. They weren't to such an extended range of Enabler/Components. Then some difficulties arose for specific enablers, which is completely understandable. Let me thank you all the effort to overcome all difficulties in such a context (uncertain for ongoing strategic decisions, challenging for using new tools and procedures, and miscommunication for being summer time). In my opinion from now on, given the DoW has been approved with great support, and most important changes in tools and processes are already in place, it all should be smooth until the end of the project. It's important to bear in mind, we must provide quick right support in the help desk, and to improve GEI's quality for FIWARE users. Well, let me thank you again for your effort, contribution and cooperation!! Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telefónica Digital Parque Tecnológico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 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/20151023/dc9da4a2/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy