Thanks Thierry for sharing your concerns!! Let me clarify some assumptions we might have: · The sprint transition mail refers to updating the backlog. Mainly I refer to the trackers. Alignment of the wiki with the trackers can be done later. We don't want to break at this time the consistency created for external observers during the last months following Miguel directions. · Updating items in the tracker not only refers to features belonging to the Roadmap, it also covers other items as you know: workitems, bugs, user stories, etc. that may not be identified in the Roadmap. I mean if your sprint content was mainly driven for technical debts you incurred, or unforeseen task arisen, you should also declare the corresponding items in the tracker. · The technical roadmap should be updated at the beginning of the major release. I recall having launched an email on this regard by first July. Due to R2 delivering, holidays and campus party, I haven't emphasized it much, but certainly it's a task we must do the sooner the better. In any case, the agile methodology has this heart beating feature making all of us to look back to the last month, and to look ahead to the next month. And this way to make us our minds so that our action is more aware of objectives, difficulties, etc. I hope it helps, otherwise, don't hesitate to let me know. Kind regards, Manuel From: thierry.nagellen at orange.com [mailto:thierry.nagellen at orange.com] Sent: lunes, 02 de septiembre de 2013 19:44 To: MANUEL ESCRICHE VICENTE; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: RE: Sprint transition - from S3.1.2 to S3.1.3 Hi Manuel The update of the backlog is one thing we have to do of course but based on the launch of FI-lab we cannot just say that we are in the middle of R3.1 without to have: · The roadmap and associated features for R3 (not only R3.1) => typically what can we do without the description of the features for R3.1? · How and where to improve all guides: we should use only the public wiki but because of the Campus Party we cannot do it before the end of the week, but we also cannot wait for the end of R3.1 to do the relevant updates We spent lots of time during the summer to improve the quality of what we deliver. We cannot now just target a specific topic or the quality will get down again. For me we have to discuss all these points during the next WPL/WPA meeting to decide a common solution, a way to manage intermediate release and a way to evaluate everything for all minor release, but first step to develop anything concrete should be the Technical Roadmap... BR Thierry De : fiware-wpl-bounces at lists.fi-ware.eu<mailto: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é : lundi 2 septembre 2013 18:09 À : fiware-wpl at lists.fi-ware.eu<mailto:fiware-wpl at lists.fi-ware.eu>; fiware-wpa at lists.fi-ware.eu<mailto:fiware-wpa at lists.fi-ware.eu> Objet : [Fiware-wpl] Sprint transition - from S3.1.2 to S3.1.3 Dear Partners, Let me remind you that we have finished sprint S3.1.2-M28 and have started S3.1.3-M29 http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates Please, update your GE backlog accordingly: * Close the backlog items finished during M28. * Update on-going items not finished yet to belong to S3.1.3 This task shouldn't take you more than 5 minutes!! Find below the links to the backlog reports, there you'll find tabs for each GE. By clicking on the ticket number you can easily access each item on the tracker and update its status and sprint. WP3: https://forge.fi-ware.eu/docman/view.php/27/2791/FIWARE.backlog.apps.report.20130831-1531.xlsx WP4: https://forge.fi-ware.eu/docman/view.php/27/2792/FIWARE.backlog.cloud.report.20130831-1531.xlsx WP5: https://forge.fi-ware.eu/docman/view.php/27/2795/FIWARE.backlog.iot.report.20130831-1532.xlsx WP6: https://forge.fi-ware.eu/docman/view.php/27/2793/FIWARE.backlog.data.report.20130831-1531.xlsx WP7: https://forge.fi-ware.eu/docman/view.php/27/2794/FIWARE.backlog.i2nd.report.20130831-1532.xlsx WP8: https://forge.fi-ware.eu/docman/view.php/27/2796/FIWARE.backlog.security.report.20130831-1532.xlsx Once the previous task is over, you've got this week to plan and schedule tasks for your GE and update your GE tracker. You can use the previous spreadsheet for items already declared, it's all about changing status and sprints. Changing these items on the tracker shouldn't take you more than 5 minutes. Next week I'll meet WP Leaders in order to review all GE's backlog. I expect your contribution to have all of them reflecting your activities. I'll be also available to meet GE owners if needed and requested. Congratulations to Susana Gonzalez-Zarzosa and Antonio García who have their GE Context-based Security & Compliance in the security chapter in perfect shape: already closed the sprint and already scheduled next sprint!!! Thanks all for cooperation!! If anything, 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 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. ________________________________ 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/20130903/3c123132/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy