Dear Partners, Find below the global retrospective from sprint 5.1.3. It is also available at the corresponding JIRA ticket. https://jira.fiware.org/browse/COR-533 Global Retrospective for Sprint 5.1.3 WHAT WENT WELL ACHIEVEMENT FEELING. Apps * FIWARE and oneM2M integration was successfully presented using a demo in the "ETSI M2M Workshop 2015 featuring oneM2M" workshop. * Improved stability of WireCloud due to the fix of some minor bugs * Most of the planned developments has been achieved * Project management tools has been created (Jira, Backlog, etc) Cloud * Most everything went smoothly * Met most our planned development goals Data * Cooperation from the FILAB people with the GE owners for the testing of images and blueprints * Help from FIWARE coordination with readthedocs issues. * Most of the planned items were completed during the sprint * Help desk items were responded within 24hours for CKAN and outstanding pending items from several months ago were completed during the sprint for this GE. Situation for the GE has improved significantly. IoT * No feedback received Security * Work has continued but not to the extent it was initially planned. This mainly due to the Holiday season WebUI * Incoming bug reports all handled, bug fixing went well Ops: * Good progress in key activities like Maintenance Calendar and Glance Synchronization as far as the front end (GUI) and the main backend functionalities are concerned. * Keystone Distribution activity made significant progress even though it is not yet completely addressed Academy: * The activities for the new theme are proceeding, we're in contact with Ogilvy. Base theme selected. Catalogue * LDAP functionality as applied to the Catalogue has been completed and is in production * SearchSideBar functionality of the Catalogue has been completed and is in production WHAT TO IMPROVE: BLOCKADE/RISK FEELING GOALS/TARGETS/OBJECTIVES * APPS - We were not able to get our work validated: we worked on look & feel (creation of a FIWARE theme for SpagoBI), we created a prototype for the new user menu, we tried to have some people involved in the validation phase but we didn't receive any reply and we lost time. * CLD - We need to get Storlets installed on at least one of the labs * CLD - We need to get the Docker Container Service up and running with at least one significant FIWARE workload. * CLD - Need to move to the community in order to evaluate like new component. * CLD - Not enough available resources to do more activities. * OPS - the deployment of the new monitoring architecture based on Ceilometer + Monasca encountered some difficulties and should be completed during the next sprint due to the holiday period this sprint was very short causing a mis-planning of the tasks * OPS - Some difficulties in completing the implementation of the backend of some key activities (Maintenance Calendar and Glance Synchronization) LAB * DATA - The way FIWARE runs the image script and blueprint is different from a standalone run, and this makes debugging very difficult. TOOLS: * SEC - timely Delivery of tooling (and complete set of instructions) to generate deliverables pending (focus on Manuals ad SW deliverables) OTHERS: * WEBUI - Many partners where already in holiday during most of the sprint. This resulted in a limited progress compared to other sprints. * DATA - Issue related to creation of StackOverflow tag fiware-kurento still open * CAT - Nothing relevant TEAM: COMMUNICATION/RESPONSIVENESS/COMMITMENT * SEC - coordination team communication towards the chapters to inform partners on hot topics (e.g. current status of amendment, EC review, Open source community ...) * SEC - communication of mailing list caretakers towards the technical chapters since clearly lacking of visibility 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/20160127/648ae54f/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy