Dear Partners, Let me remind you of this proposal for the backlog. It was shared on 1.April but I haven't received any feedback from you. Initial proposal: 1. Explain in the report how roadmap, tracker and materializing work jointly. Additionally explain the agile dynamic. How teams decide on what items to address during the sprint planning period. 2. Organise a poll to collect input from GEI owners as an evaluation exercise. Include the output in the report - perhaps also an annex with all input received 3. Improve backlog dashboards by adding a link to the backlog items pointing to its public description. Explain the hierarchy mechanism is meant to allow the contribution to more general targets identified by epics, which unfold into features, and they into stories. Well, I have no doubt you may have different perceptions, ideas or comments in order to help outlining the action points to fulfil the recommendation received. Please, share them. Kind regards, Manuel From: fiware-wpl-bounces at lists.fi-ware.org [mailto:fiware-wpl-bounces at lists.fi-ware.org] On Behalf Of MANUEL ESCRICHE VICENTE Sent: martes, 01 de abril de 2014 17:55 To: fiware-wpl at lists.fi-ware.org; fiware-wpa at lists.fi-ware.org Subject: [Fiware-wpl] Backlog - EC Report - Addressing Recommendation #4 to Backlog Deliverable Dear Partners, Let me bother you with this issue. As you know we have recently received EC Review Report #6 providing feedback of the last review meeting held in December. According to the report there's need to take action to fulfil the recommendation requests: Summary of the report: On the positive side, our contributions have made possible that: - Deliverable 2.1.6 has been accepted, and - Milestone 17 achieved - Status: fulfilled to a certain extent On the negative side, some aspects don't meet expectations, you can find them at pages 16 and 29, summarised - Not justified removal of owner and priority fields for epics and features on public items' descriptions - Basing on just naming, the relevance of these features is difficult to impossible to judge - It is not evident which features are elaborated and why - what prioritization - It's not possible to distinguish the source of an item: FI-WARE versus UC project - No visibility on prioritisation, errors on schedule, impeded items - Missing how agile implements a mechanism to steer the achievement of an overarching goal - Breakdown of the overarching requirements (such as provided by the use cases to GEs The report gives a final recommendation for the last deliverable: 1. Open backlog, i.e. features / requirements not addressed, including details as to why / in what case they are important 2. Report on applying agile management in FI-WARE for others to learn: what was the intention; what were the benefits and which were the drawbacks; what would you have done differently 3. More details on the epics, features, user stories and work items, as their name are not self-explanatory Initial proposal: 1. Explain in the report how roadmap, tracker and materializing work jointly. Additionally explain the agile dynamic. How teams decide on what items to address during the sprint planning period. 2. Organise a poll to collect input from GEI owners as an evaluation exercise. Include the output in the report - perhaps also an annex with all input received 3. Improve backlog dashboards by adding a link to the backlog items pointing to its public description. Explain the hierarchy mechanism is meant to allow the contribution to more general targets identified by epics, which unfold into features, and they into stories. Well, I have no doubt you may have different perceptions, ideas or comments in order to help outlining the action points to fulfil the recommendation received. Please, share them. Thanks for 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 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 ________________________________ 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/fiware-wpa/attachments/20140424/6d01867c/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy