[Fiware-data] Criteria for release 5 roadmap

SANTIAGO MARTINEZ GARCIA santiago.martinezgarcia at telefonica.com
Tue Oct 6 18:27:29 CEST 2015


Hi all,

Regarding the creation of release 5 roadmap, it will be useful you take as guideline the following PM assignment criteria into consideration (taken from the DoW):


·       Discounting the PMs assigned to a partner because of its role as WPL or WPA, the rest of PMs are distributed as follows regarding FIWARE GEs/GEris it owns:

o   10% will be devoted to contribution to the chapter Reference Architecture. These resources will be linked to deliverable D.1.3.1.

o   5% will be devoted to development/evolution of FIWARE GE Open Specifications associated to the FIWARE GEris it owns. These resources will be linked to deliverable D.1.3.2.

o   20% will be devoted to development/evolution of the software associated to the FIWARE GEris it owns. These resources will be linked to deliverable D.1.3.3.

o   5% will be devoted to development/evolution and improvement of the Installation and Administration guides associated to the FIWARE GEris it owns. These resources will be linked to deliverable D.1.3.4.

o   5% will be devoted to development/evolution and improvement of the Users and Programmers guides associated to the FIWARE GEris it owns. These resources will be linked to deliverable D.1.3.5.

o   5% will be devoted to management of the Product Backlog associated to the FIWARE GEris it owns. These resources will be linked to deliverable D.1.3.6.

o   5% will be devoted to documentation of the Technical Roadmap associated to the FIWARE GEris it owns. These resources will be linked to deliverable D.1.3.7.

o   45% will be devoted to provide level 3 support and maintenance (bug fixing) of the software and related documentation of FIWARE GEris it owns. These resources will be linked to deliverable D.1.3.8. Justification of PMs assigned to these actitvities during a given sprint will be rejected if the required service level was not provided in that sprint. Level-3 support of a given FIWARE GEri comprises handling of help-desk tickets created in JIRA as well as the answering of questions in the FIWARE Q&A platform (http://ask.fiware.org) or StackOverflow (http://stackoverflow.org, tag “fiware”) associated to the FIWARE GEri. Resources initially planned to provide level-3 support and maintenance (bug fixing) of a FIWARE GEri during every sprint can be devoted to development/evolution of the FIWARE GEri if the required service level is provided.  Failure to provide the required level of support for three months in a period of 5 consecutive months can lead to discontinuation of the budget/funding assigned to the partner. Available budget/funding would then be made available for third developers who may wish to take over the activities.

Of course this does not mean you necessarily need to spend 45% of your PMs on support/maintenance and stability tasks if this is not actually required for your GE, BUT that at most you will be allowed to report 45% of your PMs on that kind of activities if there’s proper justification for it during each of the sprints.

In case your GE does not require a 45% of PMs to complete these kind of tasks during the sprints, then you will need to dedicate just the necessary percentage, and use  the rest for covering activities related to the evolution of the GE with new features development.

Hope this is helpful for all.

Many thanks,
Santiago.




________________________________

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-data/attachments/20151006/59503160/attachment.html>


More information about the Fiware-data mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy