[Fiware-data] Review of stakeholder field in the backlog of Data Chapter

Miguel Carrillo mcp at tid.es
Mon Jan 21 17:26:45 CET 2013


Dear all,

In the absence of Carlos I will take the initiative. Further to a request coming from Juanjo, I have reviewed the stakeholder field in the relevant Epics and Features of the Data chapter. As some of you might be aware, this is to satisfy a request  from the reviewers whereby we were asked to clearly add some sort of traceability in our backlog.

I have gone through the Epics and Features of your backlog and checked the status of the stakeholder field. As stated by Juanjo, the common reference  for the stakeholder field at this stage is the interest expressed by the UC Projects here:

  *   https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E

I followed these rules in my review:

  *   We will check Epics and Features (not User Stories) - those in "Materializing ... " on the wiki (not user stories)
  *   We will just check those present in Release 1 (Release 2 is obviously not well populated - we will ignore it)
  *   We will inherit the GEs with "D" or "U" ( "E" is not enough to take a UC as a stakeholder). In other words, as a general rule, take the UCs with "D" or "U" and put them in the stakeholder field of each Epic or Feature of the backlog of the GE. There may be reasonable exceptions but they need a justification.

The enclosed excel file contains my comments. To ease your work, I marked in red the cells where I ask for a change or alternatively an explanation. These do not necessarily mean that you have to change something (90% of the times they do mean that but not always) .

I also realised that some features are following a naming convention that correspond to epics (and we are also using the epic template). I recall that some Epics were "downgraded" to features but I would ask for reformatting to make it consistent, it looks bad now and ilogical for an external user.

Please take a look and update the backlog accordingly. This takes a half an hour, maybe a bit more for those who have to rename the page and reformat with the Feature template.

Deadline:  Wednesday EOB. I will check this on thursday first thing in the morning.

Best regards,

Miguel

--
----------------------------------------------------------------------
     _/          _/_/                     Miguel Carrillo Pacheco
    _/   _/     _/  _/   Telefónica       Distrito Telefónica
   _/ _/_/_/   _/   _/   Investigación y  Edifico Oeste 1, Planta 4
  _/   _/     _/  _/     Desarrollo       Ronda de la Comunicación S/N
 _/          _/_/                         28050 Madrid (Spain)
                                          Tel:  (+34) 91 483 26 77

                                          e-mail: mcp at tid.es<mailto:mcp at tid.es>

Follow FI-WARE on the net

        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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-data/attachments/20130121/113b3ff6/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Review_Stakeholder_20130121_data.xlsx
Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
Size: 25079 bytes
Desc: not available
URL: <https://lists.fiware.org/private/old-fiware-data/attachments/20130121/113b3ff6/attachment.xlsx>


More information about the Old-Fiware-data mailing list

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