Dear Manuel and All, my further comments are in light blue below. BR Pier Da: MANUEL ESCRICHE VICENTE [mailto:mev at tid.es] Inviato: martedì 4 marzo 2014 18:38 A: Garino Pierangelo Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; fiware-ge-owners at lists.fi-ware.eu Oggetto: RE: [Fiware-wpl] Backlog Content - Reviews available - request for action Dear Pier, Let me comment it step by step: [PG]: I believe this rule is not to be applied (and I believe it should be at least discussed during a WPL/WPA call before deciding to apply it): Materialising page, since the beginning of FI-WARE in my view represents *what* will be done, [MEV] OK -> this is the purpose [PG]: I would point out the tense I used: *what will be done* (not *what already done*). This implies that the Materialising page contains all Features that are or will be implemented, even in the future. This is what we did since the beginning of the project. while the Technical Roadmap represents *when* this will be done. [MEV] OK -> this is the purpose [PG]: of course OK Therefore, for me the Materialising page must always contain all the items (I refer to Features particularly), [MEV] OK -> it just points out ALL ITEMS FINISHED AND AVAILABLE IN THE GEIs [PG]: See my first comment above. at least those open and/or scheduled (for dismissed ones I agree they are present in Tracker only). By introducing this rule, I don't see real advantages, but lot of disadvantages as we need modifying again stable pages. Moreover, where should we keep the removed Feature pages? We would need a further place to 'store' all the links removed (so additional burden...) from the materialising page, otherwise we would leave pages and pages not linked anywhere within the wiki. [MEV] The advantage is to allow items defined in the roadmap and that will not be implement to exist as well. We cannot include them in materializing since that would lead to think they are available on the GEI's when they are NOT. I'd like to understand what you mean by where should we keep the removed Feature Pages - they are reachable first from the roadmap, and if finished from materializing as well. [PG]: This assumption in my view reverts the way we have usually worked so far: as said in my first comment above, at least in I2ND chapter we described first the Features and placed them in the Materialising page, then we populated the Roadmap page according to the development plans. Hence the Materialising always contained the list of *all* Features of a GE, independent of when they have been of will be implemented. Are the other chapters working differently? Kind regards, Manuel Da: 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] Per conto di MANUEL ESCRICHE VICENTE Inviato: martedì 4 marzo 2014 15:09 A: fiware-ge-owners at lists.fi-ware.eu<mailto:fiware-ge-owners at lists.fi-ware.eu> Cc: 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> Oggetto: [Fiware-wpl] Backlog Content - Reviews available - request for action Dear GEI Owners, Let me share with you the backlog reviews. Please, get them from the links at the end. Current reports have been expanded to point out the action to be taken to overcome the issue: example below [cid:image001.png at 01CF3852.2D288E20] I hope you find it helpful. There's been an adjustment to the rule caring for the synchronization of items' presence in the different sources: Roadmap, Tracker and Materializing. - Short term items (Stories, Work items and Bugs) aren't public => Only present in Tracker - Long term (Epics) and mid-term (Features) items are public depending on their status: o Dismissed items aren't public => Only present in Tracker o Closed items are present in Roadmap, Tracker and Materializing o Other status (Open, Scheduled, etc) are present in Roadmap and Tracker but NOT in Materializing. Then, if you have epics and features defined that cannot be finished or haven't started yet they can live on the Roadmap under 'Future Releases', being its status Open in the tracker. This adjustment may cause some trouble to you if you had already matched Roadmap, Tracker and Materializing, with items you're working on. Be aware than when you close those items they'll match again and the issues will disappear. I'll try to bring the last criteria missing, which is about the open descriptions next week. I'm also missing a tab with all items, which I'll try to provide next week as well. Please, be aware this is the last sprint and release, whose backlog will be reported to the EC. The report will include information about the number of issues existing. Therefore, I need to ask for your cooperation to overcome as many issues as possible. If you needed any support, please, let me know. I can help by email, chat (skype:ManuelEscriche) or hold a phone call. Apps: https://forge.fi-ware.org/docman/view.php/27/3499/FIWARE.backlog.apps.review.20140304.xlsx Cloud: https://forge.fi-ware.org/docman/view.php/27/3500/FIWARE.backlog.cloud.review.20140304.xlsx IoT: https://forge.fi-ware.org/docman/view.php/27/3503/FIWARE.backlog.iot.review.20140304.xlsx Data: https://forge.fi-ware.org/docman/view.php/27/3501/FIWARE.backlog.data.review.20140304.xlsx I2ND: https://forge.fi-ware.org/docman/view.php/27/3502/FIWARE.backlog.i2nd.review.20140304.xlsx Security: https://forge.fi-ware.org/docman/view.php/27/3505/FIWARE.backlog.security.review.20140304.xlsx MiWi: https://forge.fi-ware.org/docman/view.php/27/3504/FIWARE.backlog.miwi.review.20140304.xlsx 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 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image002.gif at 01CF3852.2D288E20]Rispetta l'ambiente. Non stampare questa mail se non è necessario. ________________________________ 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/20140305/811ff8c9/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 7402 bytes Desc: image001.png URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20140305/811ff8c9/attachment.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 677 bytes Desc: image002.gif URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20140305/811ff8c9/attachment.gif>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy