Dear Partners, Let me share the global retrospective drawn for Sprint 4.3.2 It's available at the link https://jira.fiware.org/browse/COR-363?focusedCommentId=26428&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-26428 Or find it below: Global Retrospective for Sprint 4.3.2 WHAT WENT WELL ACHIEVEMENT FEELING Apps * Almost everything went well. * The planned developments have been achieved - Almost everything went as planned * New and updated documentation and training materials has been created for the new version of the Repository Cloud * The group handled many issues from the help desk. Data * AEON Cloud Messaging GE deployed in test bed. Already aligned with FI-Core methodology. * Sprint velocity for CKAN has increased significantly. * New CEP team member started giving support to FIWARE users. * Most of the planned sprint items were finished on time. I2ND * Progresses in GE developments are in line with roadmap * Agreements on several important specifications for Robotics specifications achieved * First demo planned for the Netfloc GE Security * Overall good level of features developed and or issues fixed (incl. bugs) * Work done on Security Architecture Description. First draft produced by WPL/WPA with support of the GE owners and their team * Assuming instructions would be the same for upcoming deliverables Open Spec, Open API, Install and Admin Guide, User & Programmers guide, Chapter's lead communicated instructions and created wiki pages on Chapter's wiki for GE owners to start the editing (work started for some of the GE owners). This has unblocked the situation at a number of GE owners who wanted to proceed (start the work) WebUI * Smooth start of GE development for FiVES, Initial Release of Software went as planned * Found Apache server specific problem from GIS GE and fixed in within sprint * Increasing number of support request shows growing interest in FIWARE GE and improves communication with external users Ops: * In this sprint FIDEPLOY we have closed all the scheduled tasks. * On FIHEALTH, more of 10 tasks have been completed,. * On FITOOLKIT some activities on the integration of the SLA component are started and also the synchronisation of the images in the different regions has been completed. Academy: * The development of the Builder is proceeding with additional services and new others are identified for the future. Now the test environment is available for the new features. Catalogue: * The new GE rank functionality has been developed, tested and it is ready for production * A document has been prepared with a proposal for the publication process of the SEs * Most of the development of a new catalogue notification service (notifying the most recent updates of the catalogue content) has been completed * Some bugs has been solved * The publishing of the new GE rank functionality it is waiting for the final Project approval to the design made AGILE: BACKLOG/JIRA * Backlog management has continued to improve * I begin to like how the Backlog now works. Its performance is now better and new "Helpdesk" and "Urgent tools" make forgotten ticket tracking easier. * Demo sprint well prepared TEAM: COMMUNICATION/MEETINGS * (Cloud) The group is acting more like a team to accomplish some common goals, e.g. CDMI deprecation. * (Data) Internal collaboration between Orion GEi owner and WPL has been found effective. * (WebUI) Very good interaction with chapter beforehand to find out requirements within WebUI and to make FiVES fit into the chapter perfectly * (WebUI) Response of Lab team to handle update of recipes was fast * (I2ND) Weekly chapter meetings seen as positive for better understanding overall chapter/project requirements and their impact on GEs WHAT TO IMPROVE: BLOCKADE/RISK FEELING FIWARE LAB * The FIWARE Lab infrastructure is unstable; we got several errors that are difficult to understand, and those where related to the infrastructure. Those errors blocked our work very often. It's not clear who manages a particular region and it's very difficult to obtain resources (VMs and IPs). * I think that we are nor Trial users nor Community users, since we not just using FIWARE technologies, but instead we are developing FIWARE technologies, and therefore we need more resources for our tests. Consider also that FIWARE Lab is different from Testbed, and therefore, there is no guarantee that something that is working on the Testbed will work also on FIWARE Lab. * People are spending most of their time resolving bugs in the testbed. If we want to make any progress on enhancing current components we will have to reduce this load. Unfortunately, I do not see any plan in place that would reduce the FIWARE debug load from our chapter (cloud). Many problems should be resolved directly by the administrator of a particular FIWARE node. * Different openstack versions in different regions with different message errors No public IPs in some regions make impossible to debug bugs or problems in the deployment. * Problems with LAB still block maintenance and revision of the XML3D GeoVis bundle (see also ticket ) * Provisioning of dedicated environment for Live demo (i.e. FIWARE Lab machines) needs to be solved asap (already started working on it) IDM MIGRATION * The migration of the idm at the beginning of the sprint required some extra work that was not originally planned, so it was necessary the reschedule some tasks. * The migration of the idm at the beginning of the sprint required some extra work that was not originally planned to get everything working again. * Also, as consequence of IdM migration, the cloud portal was not working property (at least for my user) making impossible to finish some of the planned task (as update the chef recipes for Application Mashup / Wirecloud) * Migration of new keystone made changes in the code (not planning) * Regarding the integration of the new Keystone-Proxy, we have some delays in FIDeploy but now UPM is supporting the activities. SOFTWARE DELIVERY * Process for software delivery needs to be standardized and available for reference. Currently it requires too much personalized support and guidelines are not easily found. CKAN's new version deployment is now being delayed because of this. * We still have problems on Chef recipes on FIWARE Lab, even if they are working on Testbed. We are not allowed to access the Chef resources on FIWARE Lab, therefore the task is very difficult and time-consuming * Problems with LAB Blueprints hinder applying the new XML3D version to the blueprint for lab deployment of the GE. FIWARE TEST BED * General comment (not related strictly to this sprint): it is difficult to be enabled on Testbed, there is no clear guidance on how to get the required resources and tools. * Improve the process of introducing new technologies into existing test-beds - we still haven't been able to get a host on one of the test-beds to setup a Docker compute node. GUIDELINES * Timeliness and completeness of guidelines from Coordination team to deal with deliverables. For Architecture deliverable instructions came late from coordination and we had to cope with changes. But even more important at M10! in the project we are still missing tool to generate automatically deliverable from wiki (public/private) content. This is clearly unsatisfactory! * Instructions/Guidelines should be delivered upfront and not assumed to be known (since new partners in FI-CORE). This is especially true for Product Backlog Deliverable which is a fully new deliverable and for which we don't have guidelines at all. OTHERS: * Publishing User Guides and Catalog entries for new Synchronization GE implementation FiVES took longer than expected (also due to 2 weeks' vacation in May). Publishing in Catalog needs to be postponed to 4.3.3 * One day deadlines for the documentation. Time to time we get requests to do documentation tasks where the deadline is a current working day. * On FIHEALTH, activities were conditioned by the FIWARE Lab Recovery Task Force. * In FIDASH, a number of issues with the authentication have been encountered. The SLA management integration into dashboard has not yet started, closer collaboration with ATOS required. * Even if the availability of the Builder was communicated weeks ago, the requests to use the service are very low. Some internal delays in the test environment for the Platform related tasks (e.g. LDAP). * In some cases it has been mentioned that FIWARE processes should be more flexible (perceived as generating overhead), while others find them useful. AGILE: BACKLOG/JIRA * Communication between external users and Jira does not work well enough: answers are not always captured in Jira. * Although small improvements can be appreciated, backlog management still has some weakness if not solicited from outside (i.e. by CHL, Backlog manager, CHA...) * Backlog management sites sometimes are not accessible and/or navigation is slow * The closure of Sprint, when coincident with a non-working day, should be postponed to the first working day after the end of Sprint. * Retrospectives from GE owners still vary a lot. They should all be at the same level so be comprehensive and actionable from Chapter's leads (WPL/WPA) perspective. * JIRA and Forge were down several times in the last phase of sprint, this caused delays because it wasn't possible to do changes to FIWARE wiki nor get information via JIRA TEAM: COMMUNICATION/RESPONSIVENESS/COMMITMENT * KIARA Team should synchronise a bit better to manage properly the issues in JIRA (e.g. when one team member is not available for some reason) Missing IOT doesn't provide input for the retrospective --- Let me some comments: It's encouraging to read we're meeting targets and getting positive energy/feelings despite all difficulties. Congratulations!! As for the difficulties: - Yes, last sprint was very difficult for FIWARE Lab, and the impact was noticed inside and outside. The Lab Recovery Task Force led by Juanjo was created. It had a tight backlog reviewed in daily meetings. - Last month Engineering took over Lab chapter leadership, which hadn't been started yet in the project. Now we count on Alfonso as Lab Chapter leader. Welcome Alfonso!! o Some pages have been introduced in the backlog website for the account requests and their provisioning: § Requests: http://backlog.fiware.org/lab/upgradeAccount § Provisioning: http://backlog.fiware.org/lab/provisioning - Last month's last week there were networks problems impacting all tools: forge, jira, backlog, email, etc. We did our best to recover!! - I'm asking for a community account for developers after sending this email. I hope to get cloud resources for all developers, and this way make access easier to verify software and preparing demos as well. - I'm also modifying the help-desk configuration to overcome these difficulties of communication with external users. I noticed partners not used to use the help-desk find it difficult. While writing a comment is visible to external users, they don't get any notification. Therefore, there's need to email them. - When the sprint closes in a 'non-working day'... (Sunday is working day in Israel), I recommend your closing issues as you progress during the sprint and then last targets during the early last week in advance. - The backlog guidelines to produce the deliverable are none since it's produced automatically from the content existing in JIRA. This has been explained in the chapters' meetings and the management board several times, and it follows the same pattern we had. The only recommendation is 'have your backlog updated, being meaningful, and free of errors'. - According to recent input received, the tool to produce other deliverables than backlogs is being tested, and soon should be able to produce them. Well, thanks again for all your effort, contributions and cooperation!! Have a nice weekend!! 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/20150619/a7602374/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy