Dear Partners, Find below the global retrospective from Sprint 4.4.1 Global Retrospective for Sprint 4.4.1 WHAT WENT WELL ACHIEVEMENT FEELING Apps * Users can create comparisons easily * Users can retrieve the list of offerings viewed recently * Descriptions can be automatically updated. * Integration with a continuous integration system in order to improve the Q&A * Some developments achieved * Integration of the Store development with the proposed in the developers guidelines Cloud * All GEs accomplished their plan. * Coordination between GEs is going well. Data * Significant progress in the dockerization of the GEs * Almost all planned items were finished as expected. * Orion's offline reporting process to the WPL is seen positive since it helps the dev team focus on the actual development work. IOT * 3 main GEs are kept at the Backend level: IoT Broker, IoT Discovery and Backend Device Manager (IDAS). IDAS is the key component in the typical use-case I, that is being used today by developers. IoT Broker and IoT Discovery have committed to demo and deliver by Oct 2015 scenarios II and III related to those GEs. * The Gateway level is now known as "Edge level" where there are communication elements, IoT Gateways and FIWARE IoT Gateways. The Protocol Adaptor GE is now replaced by the IoT Agent modules able to run in a gateway environment. Because of this, more IoT technologies will be supported soon (previously it was only Zigbee as per Telecom Italia Protocol Adaptor) and also we wil benefit from the work being done at IDAS GEi. * The GW Data Handling will include two independent components: a lightweight CB and a Complex Event Processing. the lightweight CB is an excellent tool to enable GW to GW communications and even GW-Robots communications. I2ND * The Robotics Sprint demo went smooth * Robotics GE Platform management stable * Ofnic Sprint development performed as planned. Security * Good progress on GEs despite the period this even if some work items had to be postponed to next sprint. * New version of architecture deliverable addressing review comments was delivered final to TID early this Sprint (i.e; July 7th) WebUI * New Blueprint with bundle now working and operational Ops: * Sprint completed with a high percentage of task implemented wrt the ones planned (higher than 95%) * SLA Manager improved and integrated with Dash widgets * Released Deploy version 3 based on Fuel 6.1 (Juno) * Implemented the infrastructure of the sanity check historical data (not yet in production tough) * User Management has been implemented (not yet in production tough) Academy: * The configuration of the Academy to use the LDAP for authentication is published together with the new Course Creator role. Catalogue: * A number of features have been published (RANK, notification, help page) TEAM: COMMUNICATION/MEETINGS * IOT - In July we had a chapter Face-2-Face meeting. We could work very effectively, clarify a new architecture, the interworking between the GEs, make a clear the task distribution, and performed an updated planning for the upcoming months. Priorities for the work have changed for some GEs, which is partly reflected in their new roadmap. * WEBUI - Cooperation with the Lab support team very effective, all Lab problems could be resolved * I2ND - Communication across the networking chapter part and chapter coordination has been effective in order to produce material to be shown at review meeting. * SEC - Preparation of the EC review with support of the Task leads and GE owners. WHAT TO IMPROVE: BLOCKADE/RISK FEELING FIWARE LAB/TEST BED * CLD - No process in place to stage in upgrades to FIWARE lab * CLD - No test bed for integration and test GUIDELINES * SEC - Communications on Open Specifications, Open APis, Developers' guide and other guidelines. These new guidelines came very late since on M10 !! (two months before delivery!) Whereas they were expecting to come to us months ago. In the absence of guidelines and since we were told so so far, most of the GE owners did perform the work regarding Open Spec/Open API, manuals, etc ... following the guidelines from previous project. Now they are told to cope with new guidelines which are constraining and as such are disputed. Furthermore that far more imposed rather than discussed and agreed. This is definitely something to avoid! GOALS/TARGETS/OBJECTIVES * APP - Some development has been delayed due to the need to prioritize the developers guidelines and documentation * APP - The development planned for this month has been delayed due to unexpected tasks, and to the attendance to the FI-CORE review * IOT - We still need to update the wiki to reflect all these changes. * IOT - We need to design the way to cope with communication elements and other devices at the Edge level. * DATA - CKAN FIWARE LAB instance deployment not completed yet, and new blockers being found and reported. * OPS - Documentation and testing in general is something that is lagging behind. These topics deserve more attention * I2ND - Interaction in Robotics GE components (RCM-Firos) not fully tested in the real context (Changing the environment doesn't mean nothing is changed) * I2ND - Robotics Live Demo progress has slowed down * SEC - Despite new version of architecture deliverable was delivered final on July 7th it has still not been yet delivered to the EC despite demands sent by WPA/WPL to Project coordinator. This is not satisfactory at all !! As such necessary steps should be taken by project coordinator to check and deliver on a timely basis and if not provide reasons why. As for the no feedback from peer reviewer for this second version it has also to be addressed and should not be the reason. OTHERS: * ACA - the response time of partners that blocks the validation of features ready to be published. * CAT - The check/validation (usually from the project coordinator) of features available in test should be done faster in order to avoid the accumulation of pending updates. * APPS - The review of FI-CORE has required more time than expected * CLD - FIWARE support consuming a lot of time and effort. * SEC - Karma is not satisfactory handled. Furthermore there is no Karma for project management whereas there would be good reasons to have one. AGILE: BACKLOG/JIRA * APPS - Backlog is very slow again. * DATA - Some criticism to the current support provided to users through JIRA: comment and change status published in JIRA should be received directly via JIRA notifications by final users. * I2ND - Missing timely Sprint Closures and retrospectives, compared to previous Sprint where everything completed in time. * WEBUI - Many partners and GE owners were in vacation during whole July as communicated during the sprint planning meeting. Thus only few GE contributed to the retrospective this time. TEAM: COMMUNICATION/RESPONSIVENESS/COMMITMENT * OPS - More coordination among partners is needed in order to test what implemented: User Management is urgent but still we cannot deliver it. * DATA - Communication of completed features could be improved by GE owners, especially if it is of interest to other GEs for integration purposes. * I2ND - Interaction In Robotics team decreased slightly You have it also available at the link: https://jira.fiware.org/browse/COR-377?focusedCommentId=30183&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-30183 As you know during July the review meeting was held and its feedback has been received recently. Next days clearer interpretation of the feedback will be available with the corresponding action items to implement directives received. Let's keep improving!! I wish you enjoyed your vacations/holidays!! 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/20150827/5eb7a214/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy