Dear Partners, Let me share the global retrospective drawn for Sprint 4.3.1 It's available at the link https://jira.fiware.org/browse/COR-309?focusedCommentId=21739&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-21739 Or find it below: Global Tech Retrospective for Sprint 4.3.1 WHAT WENT WELL ACHIEVEMENT FEELING * Almost all the planned work has finished successfully and updated the catalogue with new content. Moreover some bugs and help desk issues has been closed. * The new version of the catalogue (with the new look&feel) seems to have been well accepted * Most of the planned work for the sprint was finished successfully. * GE developments progressed as expected, despite issues sometimes appearing * An updated version of Kiara GE is ready * In this sprint FIDEPLOY and FIDASH are on the right path. They have completed all the assigned tasks. In FIDEPLOY I have organized a first webinar to IBM, because they would like to work on the integration of two new components (Nova, SWift). * Made good progress with the POI discussion, now also on FIWARE POI Mailing list. * Nice presentation/demos at sprint review call * New GE implementation (FiVES/Sync GE) * Strong contribution to FIWARE review (presentation "Collaboration with Use-Case Projects") AGILE: BACKLOG/JIRA * Planning and monitoring activities is always easy with Jira * GE owners were much more responsive with Jira issues and following the FIWARE agile development process. For instance we have gone from hundreds of issue with errors to almost none at all. * Planning and closure meetings are found useful to discuss/clarify about the general processes to be followed * Backlog review and management tools have helped improving significantly the adherence to FIWARE processes. * GE developments progressed as expected, despite issues sometimes appearing Jira Issues Management greatly improved by the team (congratulation by the Agile manager) * Use of JIRA for what concerns activities linked to the Chapter TEAM: COMMUNICATION/MEETINGS * With the weekly meeting, a more effective check has been obtain WHAT TO IMPROVE: BLOCKADE/RISK FEELING * Some configuration activities didn't proceed as planned. We had to postpone the publication of new training material since a new stable version is not ready yet. * We created working recipes for TestBed, but we experienced some problems when moving the recipes into FIWARE Lab. Most likely there are some differences into the 2 environments. Maybe we were wrong when considering those environment to be equivalent. * There is a risk of adding too many new functions to the catalogue that would result in complicating the usage. * CKAN deployment in FIWARE Lab is not available yet * AEON Cloud Messaging deployment in the testbed had to be slightly postponed since the testbed instance for the Ge was not working properly. * Major concerns about the delay accumulated to release the backlog deliverable (formally responsibility of chapter leaders but currently under control of Agile manager) * Major concerns about the delay accumulated to release the architecture deliverable. Draft version available but lack of instructions to perform peer review and final delivery are preventing chapter leaders to complete this action. * Process to get the GE in the catalogue is not clearly defined (and add people to an entry blocks review) * Still a number of issues outside of the pure scope of the Chapter and which impede some of the work. Here we can refer to missing clear instructions and tooling from Coordination team to generate deliverables and especially the ones now overdue (namely Architecture deliverable and Product Backlog deliverable). This would have to be addressed seriously by Coordination Team at next Sprint. * New issues with FIWARE Lab, holding us back several days (Access Control/IDM related) * Still too many old issues and some slow responses AGILE: BACKLOG/JIRA * It's not clear how developers can add new stories to a feature that is already closed. This is supposed to be correct since the methodology is defined as "agile", but when I attach new stories to a closed feature, backlog management system highlight the feature and the stories as incorrect. * It should be clarified if (and how) the demo meeting efforts will be tracked in JIRA * Still extra work to fix a number of issues on the backlog which could have been avoided if we had better guidelines to avoid this to happen TEAM: COMMUNICATION/RESPONSIVENESS/COMMITMENT * Communication between chapters. IdM team is going to deploy a new version on FIWARE Lab with some backward incompatible changes, we were notified using the same channel as normal FIWARE Lab's users. * We need act more like a team. Each GE is functions well on its own, but since we are not acting as a team with a common goal there is no synergy between our efforts. We have initiated an integration effort to include Linux Containers as part of a "beta site" in Spain. This may help * A formal 'FIWARE' email that can be sent to external users redirecting them to the FIWARE support channels should be available for the GE owners * Still responsiveness of GE teams should be improved for particularly important and urgent issues. * In my opinion all partners should collaborate more proactively. For example, regarding the integration of the new Keystone-Proxy, we have some delays in FIDeploy because the support of UPM is low. We should also improve the average of the closed tasks (now is at 46%). ---------------- Missing IOT doesn't provide input for the retrospective Let me some comments: - Deliverables are being rescheduled. The coordination team effort were sucked on closing Fiware-I, attending help-desk requests, giving support for the agile dynamic and configuring and creating backlog tools (JIRA, Backlog Website, help-desk), and FIWARE LAB. - Many things are written about agile methodology coming from Fiware-I, it's true the current implementation of the backlog is different since we're using JIRA and the backlog website. Written content will be provided as soon as possible. Meanwhile, support for it is life, you can ask me on any sprint planning and closing meeting, or send me an email, contact by skype or even phone call. However, I find complains on aspects already written but not read on the sprint planning and closing issues - it's a bit weird. Anyway, as I said we're giving full support life. - Specific effort devoted to demos can be declare as work items, obviously. However, let me emphasize these demos contents should come from achievements and progress naturally. Otherwise, we may be doing something wrong. The demos aren't the target, but a stepping stone, on the same path we're following. I think we're improving step by step - let's keep pushing. Thanks for effort, contributions 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/20150521/e8cbde16/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy