[Fiware] Backlogs content - usefulness & visibility

[MANUEL ESCRICHE VICENTE]

Dear Partners,

Let me use this channel for conveying this message about the backlogs usage.

You may know TID is working to overcome the unreliable status of the backlogs with a different approach since March; when, after an initial analysis, a proposal was made to the management board, who approved it in April. From TID coordination team, with the cooperation of the work package leaders and general enablers' owners, we have been doing an effort to steadily improve the status of the backlogs according to the resolution taken.  For that purpose, some tools have been implemented to identify errors, and to allow GE owners to have better view of their corresponding backlogs. Although the process is not finished yet, we can now say the backlog's actual status is much better. Some chapters are approaching their error levels to the zero-error zone.

In addition to cleaning the wrong/bad content, you may have noticed we're doing an additional effort to follow the agile dynamic. We are marking clearly the times for closing the sprints and for planning them by sending reminders by emails, and by providing graphs which make visible how backlogs at Chapter and GE/GEImpl level are evolving.

Above this work context on the backlog, as you know the last review report rejected most of the backlog deliverables, and confirming that our internal action line was correct.

At this stage, we think there's need to increase the backlog usefulness, since it's an important way for all of us to see, know, understand, inform and control, included the EC and reviewers, what our actions are to address important general topics.
Some of the topics requiring visibility in the chapter's backlogs are the following:

·         Work/Tasks done for the catalogue - and its associated QA process

·         Work/Tasks done for delivery documentation - and its associated QA process

·         New features/tasks derived from Luzt's reports

We want to be able to extract reports by topic in order to demonstrate the EC what work has been done to overcome specific hot issues, as those already mentioned. Although I'm in charge of supporting this action line, this way to proceed need everybody's cooperation. Let me request it from you at this point.

In a few days we'll extract the backlog snapshot, which will be delivered to the EC. We also want to give visibility on those topics with dedicated views.

My proposal/directions for the topics above are the following:

·         Catalogue -> FIWARE.WorkItem.<Chapter>.<Enabler>. Catalogue.<...>

·         Delivery -> FIWARE.WorkItem.<Chapter>.<Enabler>.Documentation.UserGuide.<.....>

·         New features/workitems derived from Luzt report -> include in the description Source =Luzt Schubert Report

Hoping you also find it sensible and useful.

If anything, please, don't hesitate to let me know.

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 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/attachments/20131030/aec662c4/attachment.html>