Dear Partners, Find below the summary retrospective for Sprint 4.2.1 Issue: http://jira.fiware.org/browse/COR-192 Global Retrospective for Sprint 4.2.1 WHAT WENT WELL ACHIEVEMENT FEELING * Cloud - Good progress with the individual GEs. * Data- planned items for this sprint have generally been accomplished and No technical impediments in the GEs for progressing the work. * The robotics demo has been successfully delivered and it has been demonstrated how a web developer could actually start and move a robot without much knowledge of ROS. This sprint sets a good base for future developments related to creating new applications that make use of the Context information provided by robots. * The development of the first version of the new look at feel of the catalogue, including the planned new features (tags, improved search, update GE contact information), has been completed and installed in the development platform AGILE-BACKLOG-JIRA * Satisfied about sprint planning * Sprint planning work went smoothly compared to previous sprint, * understanding has improved (what and how to report issues) this even if there is still room for improvements, * overall sprint planning and sprint closing have been considered useful, * Found the backlog site very useful to summarize and identify problems * The new backlog website dashboard is very helpful to identify gaps and to prioritize * Clearer picture on how to reformulate roadmap ítems (epics vs features vs User stories vs Work Ítems). * The usage of jira is consolidated for managing all the various activities related to the infrastructure running the FIWARE Academy OTHERS · Robotics - The face-to-face meeting has been very effective, and allowed to better define the next steps WHAT TO IMPROVE: GUIDELINES * Need to review the guidelines and tutorials (ie. the documentation about Deployment) * Project wide: there is a major concern about the fact that there aren't yet available guidelines to provide next deliverables (e.g. the Architecture). The chapter keeps on going by adopting earlier guidelines, but this doesn't avoid the risk that, should new guidelines be applied, the work will need to be done again with consequent waste of time/resources. * Especially we are still awaiting for instructions on how to privately edit what needs to be edited for fiware follow-up project, this even more there is so far no fiware private wiki created for follow-up project, last but not least the team was prepared to work on deliverables planned for Feb BUT still awaiting for clear instructions to get it properly done COMMUNICTION/RESPONSIVENESS/COMMITMENT * as for work items impeded they have been partially answered so why they have been re-conducted to Sprint 4.2.2 hoping information with all the details would have been provided at that time * Although a much better use of the agile methodology and tools was showed in the Sprint, an additional effort is required by GE owners, to make sure that we meet the deadlines without the need of continuous push by chapter leader. * Communications involving Robotics GE owners to be improved. Effort to synchronise better the working styles, and the interactions among groups, needs to be put by chapter and architect leader OTHERS: * The activities related to the monitoring, review and support of the training material have to be moved in the context of the Task 3.2.2 in a dedicated component. This is to be more aligned with the activities described in the DoW. * The referred software development has taken more time than initially planned, due to need to adapt the previously developed software for the new features (tags, improved search, update GE contact information) to the new look at feel of the catalogue. * The coordination towards the sprint demo did not work well - need to come with an internal process to decide on scope and responsibilities, to reduce the per-sprint coordination overhead. * Integration with external components in the GEs and their prioritization, needs to be more carefully analyzed, in some cases. * Complex Event Orchestrator work needs to be started straigthaway. Too much delay on this enabler due to scope redefinitions. * Some documentation from various GEs in the chapter is still missing in the Forge. ---------------- Missing IOT and WEB don't provide input for the retrospective Missing Retrospective from some GE Owners in some chapters Let me some comments: It's great we're improving. Let's keep pushing!! On the guidelines topic, as far as I know, the general statement is that we keep maintaining same procedures as before. Specifically for backlog review they have been detailed in the issues However, if you feel a specific deadline is blocker to your work, please, create the corresponding issue, assign it to the corresponding manager, and set its priority as blocker On the communication topic, from the backlog perspective, it has been created the http://backlog.fiware.org/urgent page to make it easier to search overdue, blockers and impeded issues. If we pay proper attention to it, we should be able to work fluently; ideally, this page should be completely clean, it would mean work is fluent and in time. On the commitment topic, I noticed lack of attendance or retrospectives from GE owners, I wonder whether the karma has also to be extended to them. On the integration topic, it's on my back to create a specific tracker for Global-Level epics, features, etc, which are defined by architects. Thanks all for 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-chapter-leaders/attachments/20150211/61a6c139/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy