[Fiware-wpa] Adoption of JIRA as tool to deal with interaction with FI-WARE Users

[Juanjo Hierro]

Dear all,

Some of you had already left our joint WPLs/WPAs confcall when we
address the matter, but we had the opportunity to discuss the matter
about what tracker tool to use to handle the interaction with final
users of FI-WARE (i.e., enhancement requests, bug reporting, requests
for information). When I refer to users, we should look beyond the
current list of UC projects in the FI-PPP but also app developers,
particularly SMEs and web entrepreneurs that will become users of the
FI-WARE Open Innovation Lab (OIL) and develop app with FI-WARE technologies.

After an internal analysis, comparing JIRA and the FusionForge tracker,
we believe that the right decision to make is going for JIRA. This
proposal was discussed with the representative of WP9/Tools (Davide)
during the WPL/WPA confcall and we rather appreciate their positive
feedback, not only because their knowledge in both tools but also
because we were concerned about potential impact on the work we are
doing in FI-CoDE.

JIRA is probably nowadays the most widely used and well-scored tool for
tickets tracking and backlog management. It is used extensively and
probably many of your companies are already using it. It is much better
than the FusionForge tracker in terms of usability and, very much
important, the ability to generate statistics that may help us to
follow-up and report how demands of users are being attended. Both
aspects would be essential in deciding what tool to adopt in interaction
with users of FI-WARE.

Please note that the use of JIRA would be limited to handling the
tickets that users/developers of the FI-WARE GEis and FI-WARE Open
Innovation Lab may create and we have to handle.

A potential issue may have to do with license costs. The first good news
is that JIRA comes for free in the case of open source projects.
Therefore, JIRA instances used to handle tickets linked to FI-WARE GEis
would not have any costs. Regarding FI-WARE GEis that are not open
source, the costs is very limited (around 10€ per user/month and users
who issue tickets do not count, just the users that will manage the
workflow of tickets, that is FI-WARE GEi owners or the team that will
operate the FI-WARE OIL). Still pending of careful analysis, we believe
that FI-WARE has enough budget to cover the costs without this requiring
to touch any of the funding from partners.

Hope you will feel excited about this decision as we are. Please share
with your teams and get back to us if you have any issue and or concern.

It is our intention to communicate the adoption of JIRA for managing
interaction with FI-WARE users in the upcoming FI-WARE Architects Week
beginning of April.

Best regards,

-- Juanjo

-------------
Product Development and Innovation (PDI) - Telefonica Digital
website: www.tid.es
email: jhierro at tid.es
twitter: twitter.com/JuanjoHierro

FI-WARE (European Future Internet Core Platform) Coordinator
and Chief Architect

You can follow FI-WARE at:
   website:  http://www.fi-ware.eu
   facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
   twitter:  http://twitter.com/FIware
   linkedIn: http://www.linkedin.com/groups/FIWARE-4239932


________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx