Dear Partners, Sorry for belated retrospective. Please, find it below: Global Retrospective for Sprint 4.2.3 WHAT WENT WELL ACHIEVEMENT FEELING * We have closed the sprint with no delay and a good cooperation between partners * Tech roadmap for the GEs is being regularly updated as new requirements arise. * The development activity of the GEris went according the roadmap without major deviations. * Demo meetings performed as expected * Architecture description completed * Contributions to live demo deliverable completed * Scheduled Features could be mostly addressed without any problems. Development of new Features worked as scheduled for most people * In this sprint we have placed on the right way Health, completing several stories and writing a first version of the documentation. In Deploy we have completed and improved some features. * We have also started a discussion with the Cloud Chapter, and we have chosen as target OpenStack release the KILO. For the Deploy component it is an important decision. * During this sprint lots of effort was translated to the stabilization of the PaaS and SDC manager due to the huge number of incoming messages that we receive due to the different developer's week. Regarding monitoring component we was more centred in installation of the new version of the components in Spain and develop a workaround to be used in case of Essex version. Policy Manager we correct some bugs detected in the component and deploy the new version of the component. Related to Murano, we finish our contribution on time and these blueprints was included inside of the core of the component * The new version of the Catalogue, with a new look and feel and new functionalities, has been published in the production machine. * Some bugs, associated to the new version, has been identified and solved * The development of the course builder is proceeding well, beta version to be released on time. AGILE/BACKLOG/JIRA * We have used the Review feature in the backlog , that helped us very much in discovering errors on Jira * Manuel support for Sprint closing and planning was very effective * We've learned to use JIRA tickets better. It's nice to be able to see in graph form what progress has been made on open tickets. * Continuous help from the Agile coordination, much appreciated by new members in the chapter to understand FIWARE rules and processes. * Improvement in the management of JIRA issues by GE owners were appreciated in the period * Improved backlog management dashboard makes it easier dealing with the errors identified * The new features of the backlog management website were received very positive. It helped to understand what was actually asked for, e.g. in terms of ticket naming * Manuel's support in sprint planning and closing meeting was again very helpful * The usage of the Backlog Management application is now clearer and errors in naming convention can be fixed easily. COMMUNICATION/MEETINGS * Weekly chapter meetings seen as positive for better understanding overall chapter/project requirements and their impact on GEs. WHAT TO IMPROVE: BLOCKADE/RISK FEELING * We're worried about the availability of FIWARE environment for the next Demo usage * Availability for new CKAN release in FIWARE LAB is taking much longer than expected. CKAN team reorganizing in order to be more efficient. * We would like to have more feedbacks about the interactions btw ET and other GEs involved in the Robotics Live demo, i.e. what about the Wire Cloud GE involvement status? * The overall project seems to suffer a bottleneck effect due to too many final decisions in the hands of project coordinator; this can impact on timely release of planned deliverables (e.g. architecture deliverable, decisions on open call, CA, etc) * A lot of travelling at DFKI, slowing down coordination work and postponing POI discussion several times during this sprint * For DASH component, some delays are occurred in the development activities, but I am confident that they will overcome in the next sprint. In Toolkit I have not seen any progresses in this sprint. A warning message will be sent by me. * The integration of the LDAP is proceeding slowly because of configuration parameters are not provided yet. * There is pending a decision on the new functionalities/changes that will be associated to the next version of the Catalogue (and the respective priorities). A first list is available AGILE/BACKLOG/JIRA * We have found (since the last update) that the backlog takes so much time to load the information of one enabler: it would be better to fix it. * For some GEs, part of the work performed during the sprint has not been reflected in Jira (specially the work related to solving requests about the GEs from external users). * Items in Jira should be updated timely and reported in the weekly meeting. CKAN and Big Data GEs will have various items moved to next sprint that might actually have been finished, but were not reported in any way. * The processing rules for backlog verification should not change while on going, in order to avoid waste of time in rolling back tasks already done. Moreover, some rule appears contradictory (e.g. GE-GEI name in the issue summary, or request to avoid blanks, which is not the case of issues coming from coordination tracker - they are usually expressed as plain text, no hierarchy at all, blanks used). * It should be clarified how live demo effort will be tracked in the FIWARE process, e.g will it be defined as User Stories in JIRA? * Still expected a better responsiveness by some GE owner when managing JIRA issues (and providing retrospective) * JIRA crash caused some lost tickets that had to be re-created * Backlog got slow and a bit unresponsive or was offline sometimes COMMUNICATION/RESPONSIVENESS/COMMITMENT * The collaboration and interaction within the chapter is still low, and the partner must be always encouraged to participate ---------------- Missing · IOT doesn't provide input for the retrospective · CLOUD chapter doesn't provide summary retrospective although some GE Owner did provide it. · Missing Retrospective from some GE Owners in some chapters ---------------------------------------------------------- I'm glad to read on achievement feeling and good cooperation, let me also appreciate the positive comment on Agile/backlog/Jira, and answer some of the proposed improvements : - JIRA was upgraded since the crash was 'implicit' to the version we were using. - Backlog management website architecture was modified to make it responsive again. - Rules are stable but we don't have rules for everything. When new significate deviations appear not following most used patterns then I react to them. - Global Tech tracker is underway but not available yet. Sorry!! - Yes, I also miss cooperation from some chapter leaders and GE owners to timely complete the set of simple tasks to properly follow agile like: closing the sprint planning or provide the retrospective. These rules are there, they are stable but they are not followed by some partners. Well, let me thank you for the good performance and cooperation!! Let's keep doing again the positive effective things we do well, and modifying those we should improve. Have a nice day!! 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/20150421/6b783787/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy