[Fiware] Agile: Retrospective for Sprint 4.3.3

[MANUEL ESCRICHE VICENTE]

Dear Partners,

Find below the global retrospective from Sprint 4.3.3
Global Retrospective for Sprint 4.3.3
WHAT WENT WELL
ACHIEVEMENT FEELING
Apps

  *   New APIs
  *   Stores and offerings can be ordered by score and can be reviewed as well
  *   Better GUI
  *   A new installer intended to easy the installation process of the Repository has been created
  *   Dependencies used for the OAuth2 authentication have been updated in order to allow a better integration with the new version of KeyRock
  *   All the planned developments for the sprint have been achieved

Cloud

  *   The technical work progressed smoothly
  *   Problems emerging from the FIWARE lab were handled promptly

Data

  *   Most GEs finished their planned sprint items as expected on time.
  *   More availability by the persons in charge of managing the LAB in order to help the CKAN team.

I2ND

  *   KIARA GE Published in FIWARE Catalogue.
  *   GEri developments gone forward without roadmap's deviation
  *   Netfloc Demo was performed during demo meeting, which included two showcases:
     *   ODL based application for tenant isolation
     *   ZHAW physical testbed setup; bridges and interfaces creation when launching OpenStack VMs
  *   Netfloc architecture and demos was shown at SDN workshop and at a booth presentation on OpenCloudDay in Bern, Switzerland
  *   Could test a first version of RCM belonging to Robotics GE
  *   Live demo architecture (Robotics) almost decided

Security

  *   Most of features planned in last Sprint of Minor Release 4.3 have been delivered
  *   Good progress regarding fixing issues in helpdesk
  *   Update of Architecture desciption (overall + GEs' architecture) was properly addressed by all (comments received from peer-reviewer - DFKI - were analyzed and addressed/answered)
  *   Issue faced with Privacy GE was analyzed and discussed also caused creation of a dedicated Task Force involving (Privacy GE owner, Sec Chapter's Lead a Architect, CA and Reviewer). It was properpply mananged to explore potential solutions and come up with a decison shared and agreed by ALL (i.e. not to include Privacy GE Architecture in D17.1.1 due to issue faced with a Library form IBM not Open Source).

WebUI

  *   Scheduled new server and example client features implemented and delivered on time, creating combined delivery out of this went really smoothly (GIS Data Provider)!
  *   Implementation of FiVES communication layer went without problems due to well document Synchronization GE specification
  *   New Chef recipes created and delivered to SVN after verification, these completed also on time (GIS Data Provider and XML3D).
  *   Despite constant issues with the lab, response time of the lab team was mostly quick. There was constant dialogue about the problems which in the end led to solving at least most of the major issues

Ops:

  *   FIDeploy has completed 100% of planned activities.
  *   FIDash has completed the integration activities of monitoring services and support of multi-region. A basic integration (embedded) of SLA manager was started
  *   FIToolkit, almost all activities regarding the glance sync have been completed
  *   FIHealth GUI's was improved and almost all planned activities have been completed

Academy:

  *   development is proceeding, the builder is published and some user is asking for credentials, with this release it will be possible to login using the fiware forge account

Catalogue:

  *   The GEiRank functionality has been completed and tested in the development platform. The publication in the production platform is waiting to the final approval of the project managers.
  *   An analysis of a search side bar functionality has been completed.
  *   The notification services for catalogue content update functionality has been completed and tested in the development platform.
  *   The helpdesk contact functionality has been completed and tested in the development platform.

AGILE:BACKLOG/JIRA

  *   http://backlog.fiware.org seen in some cases more useful than Jira and the wiki since it summarizes everything in a single place.
  *   (I2ND) Sprint closure timely achieved by all Teams. Retrospective provide in time as well.

TEAM:COMMUNICATION/MEETINGS

  *   (Cloud) Good collaboration with the partners regarding containers strategy
  *   (I2ND) Collaboration between participants (Robotics) improved
  *   (I2ND) Weekly chapter meetings seen as positive for better understanding overall chapter/project requirements and their impact on GEs
  *   (Ops) There's good collaboration among partners in particular with UPM-ETSIT for the KeyRock 2.0 integration and IBM for the Docker integration

WHAT TO IMPROVE:
BLOCKADE/RISK FEELING
FIWARE LAB

  *   Cloud is not working well.
  *   Cloud issues in the FIWARE Lab have generated problems while testing the installation of the software
  *   Cloud issues in the FIWARE Lab have slow down the development process, during the testing phases
  *   FIWARE Lab is still unstable;
  *   Automated regression tests in each region required to support upgrades and configuration changes.
  *   Constant impediment of work on the bundles was very time consuming. As Lab user, the error messages that showed were not really helpful, and often, there were none at all.
  *   Inconsistencies of software versions and infrastructure status across nodes are not only confusing, but also lead to that even though recipes are successfully deployed on the "reference node" Spain2, it's not guaranteed that the software will work everywhere in FILAB.

IDM MIGRATION

  *   We still have some problems with IdM REST API version 2 that block the global instance update.

FIWARE TEST BED

  *   Need a way to work on a LAB test bed, there should be a "developer lab" that is part of the FIWARE global labs

GUIDELINES

  *   I don't know how to name Demo tasks
  *   documentation on how to create images on Testbed is not updated; moreover there is no documentation regarding security
  *   The instructions to prepare Training material seem to be cumbersome. I also ran into a problem trying to edit the catalog. I am unable to log in, I am unable to reset my password, and I get refused to define a new login because my email address is already identified with an existing account.
  *   GE delivery Guidelines came late (on Month 10!) and rather impose than propose
  *   No clear or late guidelines. Assuming we could go for guidelines from previous project can be wrong as such we need clear guidelines, specific to FI-CORE/FIWARE (would they be leveraging on previous ones or not).
  *   Since review for the previous project is finished, we need to know what and how to cleanfy things (e.g. Wiki) in a coordinated and harmonized manner. Once more instructions at Project Level are here also pending.

OTHERS:

  *   Lots of tickets related to the upgrade to community account user in Spain that required lot of efforts of the team.
  *   The problems in the FIWARE Lab node, especially in Spain, has translated effort to the support and maintenance node.
  *   Slow progress in CKAN deployment & availability as GE: CKAN team points to a confusion on the necessary requirements
  *   Interaction/integration of Robotics GE components still at first stage and to heavily improve
  *   Info from other parties (e.g. external GEs to be used in live demo) is sometimes difficult to retrieve
  *   In FIDash there is need more effort in order to integrate and in part redesign the SLA Manager
  *   In FIToolkit, the security problem identified during the sprint had impact on the planned activities on GlanceSync
  *   Support from Open Source Team in FIWARE to issue faced by GE owners regarding GE delivery.

AGILE:BACKLOG/JIRA

  *   Backlog is very slow again
  *   Access to JIRA and backlog portals slowed down
  *   Support provided to users through JIRA is not good enough. Comment and change status published in JIRA should be received directly via JIRA notifications by final users otherwise unnecessary overhead is added.
  *   Different workflows to be followed for dealing with help issues increase the difficulty for managing them: fiware-tech-help issues must be answered by replying to the email sent by Jira, nevertheless other issues, for instance those coming from accelerators, must be answered directly in Jira with a comment.
  *   http://backlog.fiware.org could have a form in order to create new issues that are automatically added to Jira and the wiki, and also automatically materialize (in the wiki) features that are detected to be closed.
  *   Backlog management policy is seen in some cases as too restrictive (not flexible or dynamic enough) generating too much overhead.

TEAM:COMMUNICATION/RESPONSIVENESS/COMMITMENT

  *   Some sprint items in JIRA were updated or changed for others when we already were very close to the end of the sprint.
  *   Overall project communication among coordination, chapter, GE owner should be improved
  *   In FIHealth a more closely collaboration with CNET is needed in order to implement the management of historical data
  *   Communication on procedures is not satisfactory and as such needs to be improved. This was especially true at this Sprint 4.3.3 for what concerns:
     *   Procedure on how to make GEi VM images public in FILAB (lacking this procedure as impeded a task!)
     *   Procedures to obtain SSL Certificates for FIWARE GE instances in FILAB

Missing

IOT doesn't provide input for the retrospective
You have it available it also available on the link:
https://jira.fiware.org/browse/COR-370?focusedCommentId=28727&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-28727


Let me inform on how to provide support in the help desk through JIRA:

-          There are NOT different guidelines for the main and coaches help desk on how to answer the incoming request.

-          Answering can be done from JIRA by using the integrated email plug-in.

o    It's explained at http://backlog.fiware.org/guide/tracker.html#email-issue

-          We are trying to improve this procedure but some difficulties are stopping us:

o    You can read the details here: https://jira.fiware.org/browse/SUPP-262


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/20150723/3d6676de/attachment.html>