Dear Partners, Please, find below the global retrospective for Sprint 5.1.1. You can find it also available at https://jira.fiware.org/browse/COR-480 -------------------------------------------------- Global Retrospective for Sprint 5.1.1 WHAT WENT WELL ACHIEVEMENT FEELING. Cloud * The roadmap for all GE's were completed * The different activities were finished accordingly to the planned scheduled time. Data * The refactor done on Cygnus about using batching techniques; now the performance is much better * Valuable information retrieved from investigation carried out during this sprint. It will allow to better design planned improvements and features to be delivered during Release 5 Security * Delivering Open specs (except for Privacy GE due to pending decision from Coordination, only resolved 2 weeks ago) * Finalized the technical roadmap for R5 * Bugfixes * Implementing new features WebUI * Completion of feature implementation and software migration tasks * Access to Lab without any problems, which allowed thorough testing of blueprints and images * Fast response time on JIRA LAB Ops: * Some key activities for the OPS Chapter have been started and are progressing as expected: keystone distribution and new monitoring architecture * A dedicate instance of Dash has been deployed and is ready to use * The new Infographics and Status Page is ready to be deployed. Academy: * The activities for the new theme are started and there is a dedicated testing environment based on the last Moodle version. * DNS (https) for the Course Builder available and reported in the documentation. * Closing activities of monitoring and backup of the Course Builder Catalogue * There is now a more dynamic and fluid relation with Oglivy on Catalogue aspects related to UI / Look&Feel. This has allowed to solve several pending issues * The LDAP integration in the Catalogue is now ready to be published. * Several new functionalities have been finished and published (monitoring analytics, publication status, what's new) * The analysis and software development of the functionality "Add reference to developers homepage" have been completed * The functional design of the "search side bar" functionality has been completed TEAM: COMMUNICATION/MEETINGS * DATA - GEi owner providing asynchronous inputs to the meeting minutes and fluent collaboration with WPL has proved to be an effective way of working and it is consolidating sprint by sprint * DATA - Got support from technical writers for documents format change WHAT TO IMPROVE: BLOCKADE/RISK FEELING GUIDELINES * WEBUI - Testing setup for image creation task was not properly documented and therefore it was impossible to complete within deadline. GOALS/TARGETS/OBJECTIVES * OPS - Some tasks in FI-Dash and FI-Toolkit have not yet been completely addressed (integration with IDM, overcommit ratio) and are requesting too effort to complete. This caused a delay in other important activities (Maintenance Calendar). * SEC - Academy course to be completed * SEC - Issues with FILAB image deployment * SEC - Again SSL in Keystone postponed... It is difficult to find a slot to upgrade the infrastructure * WEBUI - Tasks depending on each other slowed down the overall development, e.g. Catalogue completion needs Blueprints and Images beforehand. These dependencies made it hard to match the deadlines when problems occurred during one of them LAB * CLD - We require support from one of the labs, preferably Spain2, to provide the necessary resources to create a Container Service. * CLD - Likewise, we require a FIWARE node to install Storlet support for object storage TOOLS: * SEC - Unable to log in to the FIWARE deliverable toaster app. In contact with Bitergia to fix it. * SEC - Backlog check tool is not checking previous roadmap release for R4 features, now that the current Roadmap is replaced with R5 features only * DATA - Support provided to users through JIRA is contra intuitive. Comment and change status published in JIRA should be received directly via JIRA notifications by final users OTHERS: * CAT - There remain some operational aspects, related to the LDAP integration in the Catalogue, that need to be clarified before publishing this functionality * CLD - The relation with the Open Source community give us a slow interaction to close some activities. * DATA - How short the sprint becomes when a FIWARE event is scheduled * DATA - Karma metrics measurement system is opaque * DATA - Current backlog management policy, based on excessive control mechanisms and micro-management, is a severe burden for development teams * WEBUI - There were some confusion about switch generic enablers funding discontinued, and this caused some of the backlog tickets missing in JIRA. TEAM: COMMUNICATION/RESPONSIVENESS/COMMITMENT * ACA - The overload of Ogilvy can delay the publication of the new theme. ENG team available to support and speed up this issue * DATA - Ability to have direct communication with the FILAB support (related to the new image creation process) * SM - Missing feedback from Apps and IoT chapters In general I see we are almost over with topics related to releasing R4, which means we should be able to deliver it all soon. Let me remind the highest priority in on improving quality of the enablers and reacting quickly to incoming issues in the help desks. Let me emphasize backlog management policy has NOT changed at all. The structure and model for the backlog remains the same. We keep improving the tool to provide backlogs to all areas. Backlog views allow understanding what activity is ongoing. We also keep improving the tool to understand our performance in the help desk. Since it allows accepting or disagreeing on external criticism about it. Understanding is a basic factors for any effective risk management and subsequent action. I hope I helped understanding it better. 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/20151125/43db44f4/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy