Dear Partners, Please, find below the global retrospective from Sprint 5.3.1, or in the corresponding jira ticket: https://jira.fiware.org/browse/COR-826 Please, notice we keep having problems on the team topic, I mean, communication, responsiveness, etc. Let me emphasize it's very difficult for the people in contact with users and stakeholders to provide a good service, or accurate communication when they aren't properly backed on actual problems in the Labs or Enablers. So please, let's try to improve on it. Let me emphasize some working work leaders can't progress to meet their target because of lack of cooperation from their teams. Global Retrospective for Sprint 5.3.1 WHAT WENT WELL ACHIEVEMENT FEELING. Coaches * Except few situations (mentioned in the related What to improve list), all the normal activities related to CEED-Tech were handled without any particular problem, including: Community Account assignment (i.e. FLUA tickets), incoming general and technical requests from the Startups/SMEs (i.e. HELC tickets), and review of the technical assessments (CEED-Tech). * The SpagoBI GE owner (represented by the various Engineering colleagues) was very competent in solving incoming problems and requests from the Startups/SMEs, including spotting bugs (i.e. APP-1069<https://jira.fiware.org/browse/APP-1069>) (CEED-Tech). * The support to creative ring Startups/SMEs was successfully completed (CreatiFI). * Related to FABulous: the evaluation of projects in Bilbao was very good. The assigned coach (Pasquale Vitale) confirmed that the number of projects was 25 and only 4-5 projects were very "poor"; for this reason the evaluation was a hard task (FABulous). * The Budapest FIWARE Lab node was very helpful and competent both in normal activities (i.e. FLUA tickets) and "strange" situations like migrations or similar (e.g.) (CEED-Tech, FI-ADOPT). * No FLUA ticket was received for this period (FI-ADOPT, FRACTALS, FInish, SmartAgriFood). * All the incoming tickets and requests (e.g. HELC) have been treated and closed normally (FI-C3, FI-ADOPT, FRACTALS, FInish, SmartAgriFood). * A face-to-face evaluation of all the FI-C3 SMEs took place in Paris; no big issue was detected in relation with FIWARE usage as most did implement recommendations set in previous reviews (FI-C3). * No requests have been received from the FICHe SMEs in this period (FICHe). * The assigned Coach for FINODEX (Pasquale Vitale) provided support to Startups/SMEs by using his personal email address, both answering directly to the teams and redirecting the request to other members (e.g. GE owners); starting from now, he will manage the requests by using the coaches-help-desk-jira at fi-ware.org mailing list (FINODEX). * All the normal coaching activities were carried out normally, without any particular situation (INCENSe, SpeedUp! Europe, IMPACT). Collaboration * Active collaboration with other initiatives, taking advantage of the momentum around FIWARE: evolution of the activities associated to FIWARE Mundus and in particular with respect to take-up of FIWARE by US cities as well as in the domain of standardization. * Meetings or events planned for the coming weeks for those actions, but also with TM Forum (second week of May) and the Committee of the regions (end of May). Therefore, high activity and good prospects Dissemination * These targets were met without problem, specifically: Support to NetFutures 2016. Preparation for TM Forum and CampusParty Events. Exploitation * FIWARE Commercial and Technology Workshop organized by Atos Iberia for the whole Atos Group * Identified possible PoCs and Use Cases for evaluation * Commercial evaluation (cost analysis for commercial node, revenue models, etc * CORE GROUP Monthly Meeting in Atos headquarters to prepare the Founders event in June and advance on the creation of the Foundation, discussion of the Bylaws * Working on some market analysis about IoT Platforms, Smart Cities, Smart Industry, Industry 4.0 Press Office * Conversation calendar and web/social management with no major issues. Continuation of the FIWARE Stories strategy featuring top SMEs in the programme. * Two new videos produced. * Support to NetFutures Event (materials, stand and on-site coverage) * Two new brochures (Smart Cities, Acceleration Programme Results) produced. Apps * Application Mashup has fixed a lot of bugs affecting the software released on Release 5.2. * Application Mashup has also improved the manuals * Business API Ecosystem has made a great advance in the development * Business API Ecosystem has finished all the planned user stories Cloud * Many features started and finished Data * Help desk issues generally well attended * Several CEP related Jira issues and review conflicts solved with the help from the chapter leader. * Most of the planned sprint items were completed for Orion, Kurento, CKAN and CEP. Security * Bug fixing and features accomplishments WebUI * GE development continued as planned with anticipated progress Ops: * Good progress in all the tasks of the chapter (overall Sprint Backlog Status 75,9%) New Monitoring Architecture up and running in FIWARE Lab Spain2. Academy: * The first version of the new theme is ready for validation in the test environment. Ogilvy has been notified (via email and jira tickets) to provide comments and indications. Catalogue * Positive aspects: All the functionality related to TextUnderDowmnloadsTab has been finished and put into production WHAT TO IMPROVE: BLOCKADE/RISK FEELING GOALS/TARGETS/OBJECTIVES * DATA - Still missing the publication of CKAN course in FIWARE Academy. * DATA - Several reported bugs during the sprint from the QA team related to documentation, impacted the originally planned sprint items for the GEs. Some QA reported items need to be postponed to next sprint due to lack of time for their resolution in the sprint. * OPS - still some development activities, mainly related with monitoring of new nodes and synchronization, not totally completed as planned * CATALOGUE - the definition of the Catalogue roadmap, related to further developments of the Catalogue functionality, from now on until the end of the project, has not been finished and will be completed in the next sprint * ACADEMY - Validation from Ogilvy is taking more time than expected. Send reminder and contacted via Skype. This validation is now blocking the publication of the theme * PRESS OFFICE - Mid-term planning to rationalize the use of funding, especially what is related to event production. * PRESS OFFICE - Start to think on the transition to FIWARE Foundation Branding. LAB * APP - Testbed does not work properly, therefore it is difficult and time-consuming to make tests and fix bugs on Chef recipes * CLOUD - Still need to install storlets HELP DESK/SUPPORT * COACHES - Some tickets are still opened (CreatiFI). * COACHES - Regularly closed but no comment provided: FrontierCities * COACHES - Issues still open and no feedback provided: COAC-207<https://jira.fiware.org/browse/COAC-207> - EuropeanPionners COAC-219<https://jira.fiware.org/browse/COAC-219> - SOUL-FI TEAM: COMMUNICATION/RESPONSIVENESS/COMMITMENT * DATA - Unavailability from Big Data GE owner and from SSE and SDA incubated GE owners. * DATA - Delay in architecture deliverable. * COLLABORATION - More coordination in the execution of the activities as a result of a well-defined strategy that is agreed by all members. While activities are ongoing, they are not sufficiently reported or shared in the context of this WP. Synergies come from the Technical committee meetings and overall opportunities that come to FIWARE without a priori planning. Therefore, the modus operandi so far is based on answering requests as they come-. In order to solve this, a call for a meeting between partners in this WP has been sent, still with poor answer from the members * EXPLOITATION - More collaboration from the rest of the partners in gathering market analysis and in providing strategic commercial guidelines stemming from their commercial departments * COACHING - Reactivity and availability of Prague FIWARE Lab node Team is not always present (e.g , ) and they refused to help in case of migration () (CEED-Tech). * COACHING -The AEON GE owner seems not very responsive (i.e. HELP-6402<https://jira.fiware.org/browse/HELP-6402>) (CEED-Tech). * COACHING - A long response time from the Object Storage GE owner on a ticket created some issues, but it turned out that this was mostly due to the fact that a new team member joined the GE Team, needing some time to come up with the tools (e.g. wiki, lab) (FI-ADOPT). * COACHING - Despite the numerous "pings" and requests from the FIWARE Scrum Master (Manuel Escriche) and the various Coaches, the Coach Team Leader (Stefano De Panfilis) is not covering an active role, forcing the coaches to have a "self-organization" (not related to a single accelerator). * SCRUM MASTER - Sustainability and IoT didn't provide retrospective OTHERS * SECURITY - Timely processing & closing of tickets * DISEMINATION - Still to improve the mid-term visibility with the project coordinator. * WEBUI - Work estimation for yet unknown tasks * COACHING - Related to FABulous and in according with what mentioned in the related What went well list entry: during the evaluation in Bilbao, the time for project explanations was not enough; it turned out that 30 minutes were not sufficient to explain the prototype, the business model, the business plan, and the roadmap for the next step (SML3) (FABulous). * COACHING - The networking problem that affected the Budapest FIWARE Lab node created some issues to a SME since they had a demo on the same day; anyway, the Budapest node Team tackled the issue as quickly as theY could (FI-ADOPT). Thanks all for effort, contributions and cooperation!! Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader IOT Innovation - FIWARE Initiative Telefónica Digital Parque Tecnológico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34. 983.36.75.13 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/20160525/0862526c/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy