Dear all, I'm forwarding you this important email from Manuel. Please have a look at what this report says regarding Security Chapter (see security Dashboard at https://forge.fi-ware.eu/docman/view.php/27/2864/FIWARE.backlog.security.dashboard.20130930-1803.xlsx). As you know I did anticipate to have Backlog maintenance a topic of our weekly audio conf being said this is an important topic to cover and on which to progress with help of ALL and especially GE owners. This even more that now we have no excuse because we now have the tools and support provided by Manuel. Please note that as reported by Manuel, next backlog deliverable may be structured on a GE Implementation bases with views of our burn down and flow charts (!). So please GE owners take necessary steps to address issues in copse of your GE for our Security Chapter GEs to look good at the end. Counting now on you all. Regards, Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de MANUEL ESCRICHE VICENTE Envoyé : mardi 1 octobre 2013 12:09 À : fiware-ge-owners at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] Agile dynamic - release and sprint closing -> request for cooperation Dear Partners, Find linked the dashboards produced to capture the release and sprint closing. https://forge.fi-ware.eu/docman/view.php/27/2859/FIWARE.backlog.apps.dashboard.20130930-1802.xlsx https://forge.fi-ware.eu/docman/view.php/27/2860/FIWARE.backlog.cloud.dashboard.20130930-1802.xlsx https://forge.fi-ware.eu/docman/view.php/27/2863/FIWARE.backlog.iot.dashboard.20130930-1803.xlsx https://forge.fi-ware.eu/docman/view.php/27/2861/FIWARE.backlog.data.dashboard.20130930-1802.xlsx https://forge.fi-ware.eu/docman/view.php/27/2862/FIWARE.backlog.i2nd.dashboard.20130930-1802.xlsx https://forge.fi-ware.eu/docman/view.php/27/2864/FIWARE.backlog.security.dashboard.20130930-1803.xlsx After having a look at the burndown diagrams mainly, which show how items were closed over time, I see many GEi onwers didn't perform any action to close the release or sprint. I'd need to know the reasons preventing those GEi onwers to close their items properly. In general I think we need to come to the right agile dynamic as soon as possible. I can also appreciate that some GEi owners in the following chapters Data, Security and I2ND did close the corresponding items properly, what I thank them for. The agile methodology gives flexibility when you set up your backlog, it means at the sprint planning. Afterwards, it needs us to be diligent and keep committed to the backlog. I wonder whether any of you had a chance to pay attention to the review report from the EC and read the comments related to the backlog. I'll be following the agile dynamic closely so as to demonstrate the EC that FI-WARE is working properly. In these regards, next backlog deliverable may be structured on a GE Implementation bases with views of your burn down and flow charts. In general, following the agile dynamic I think it's a shared objective, so I need to ask for your cooperation to overcome the current situation. I'm also requesting the Work Package Leaders to include in your weekly agendas a time slot for backlog maintenance. Thanks in advance for cooperation!! 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-security/attachments/20131002/a0f3f331/attachment.html> -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: <https://lists.fiware.org/private/old-fiware-security/attachments/20131002/a0f3f331/attachment.txt>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy