Hi, I am not 100% sure myself. At least we should take care the existing backlog entries. It seems that FI-WARE is tracking the performance of the WPs through the Backlog entries. If we do not have any, this might seem strange then, but given the stage of the project, I am not really sure that we should add new entries. At some point it simply adds overhead. Christof, what do you think is the best approach here? Best, Philipp Am 20.01.2014 14:45, schrieb Toni Alatalo: > How? > > Earlier we were instructed to add features to the tracker, which most of us have done. Then we’ve be updating the status as they’ve been finished etc. So I’m confused about this: > > (MIWI) "There’s nothing scheduled for the current sprint since everything scheduled are features.” > > I thought we are delivering the features now in the release, the GEis. > > I’ve marked our 3DUI EntitySystemIntegration feature as ‘completed but not delivered’ (or so) as the release is not delivered yet. Am unaware of other actions that should do and could not parse such from those mails, sorry. > > ~Toni > > On 20 Jan 2014, at 15:32, Philipp Slusallek <Philipp.Slusallek at dfki.de> wrote: > >> FYI. Please take care of the Backlog entries! >> >> Thanks, >> >> Philipp >> >> >> -------- Original-Nachricht -------- >> Betreff: [Fiware-wpa] Backlog Content: Missing updates - Hot topic: >> Delivery M33 - Sprint Planning (yet?) >> Datum: Mon, 20 Jan 2014 12:21:04 +0000 >> Von: MANUEL ESCRICHE VICENTE <mev at tid.es> >> An: fiware-ge-owners at lists.fi-ware.eu <fiware-ge-owners at lists.fi-ware.eu> >> Kopie (CC): fiware-wpl at lists.fi-ware.eu <fiware-wpl at lists.fi-ware.eu>, >> fiware-wpa at lists.fi-ware.eu <fiware-wpa at lists.fi-ware.eu> >> >> >> >> Dear Partners, >> >> By exploring the backlogs I get quite a negative perspective of the >> on-going work leading to successfully meet our commitments due by the >> end of the month. I hope it’s consequence of having the backlog >> outdated. Therefore, I’d appreciate having it fixed as soon as possible. >> Otherwise, I’d have no option but to show concern. >> >> Thanks for cooperation!! >> >> *_UPDATES REQUIRED FOR Backlog Delivery (due end of December)_* >> >> Find below the number of items needing updates in the different chapters: >> >> ·Apps (31 items), Cloud ( 45 items), IoT (40 items), Data (23 items), >> I2nd (42 items), Sec(4 items), MiWi (27 items) >> >> ·I’d appreciate your collaboration to get them updated ASAP otherwise >> they appear in red in the deliverable. >> >> Have updated the reports of the backlog: hot topic (delivery M33) and >> dashboards. >> >> *_HOT TOPIC – Delivery M33_* >> >> https://forge.fi-ware.eu/docman/view.php/27/3307/FIWARE.backlog.deliveryM33.search.20140120.xlsx >> >> I’m missing contributions from many GEIs to the current delivery. >> >> I’d appreciate knowing whether they aren’t contributing because those >> enablers put off their delivery to next release or any other reason. >> Otherwise, I’d appreciate your collaboration and create those work items. >> >> *_DASHBOARDS – Sprint planning_* >> >> *Apps*:Items: 46 = 0 Epics, 22 Features, 8 User stories, 16 Work items, >> 0 Bugs >> >> There are still enablers with nothing scheduled for the current timeframes >> >> https://forge.fi-ware.eu/docman/view.php/27/3300/FIWARE.backlog.apps.dashboard.20140120.xlsx >> >> *Cloud*: Items: 67 = 0 Epics, 26 Features, 18 User stories, 23 Work >> items, 0 Bugs >> >> There are still enablers with nothing scheduled for the current timeframes >> >> https://forge.fi-ware.eu/docman/view.php/27/3301/FIWARE.backlog.cloud.dashboard.20140120.xlsx >> >> *IoT*: Items: 47 = 0 Epics, 29 Features, 8 User stories, 10 Work items, >> 0 Bugs >> >> There are still enablers with nothing scheduled for the current timeframes >> >> https://forge.fi-ware.eu/docman/view.php/27/3304/FIWARE.backlog.iot.dashboard.20140120.xlsx >> >> *Data*: Items: 86 = 0 Epics, 32 Features, 20 User stories, 32 Work >> items, 2 Bugs >> >> There is 1 enabler with nothing scheduled for the current timeframes >> >> https://forge.fi-ware.eu/docman/view.php/27/3302/FIWARE.backlog.data.dashboard.20140120.xlsx >> >> *I2ND*: Items: 98 = 0 Epics, 36 Features, 6 User stories, 56 Work items, >> 0 Bugs >> >> https://forge.fi-ware.eu/docman/view.php/27/3303/FIWARE.backlog.i2nd.dashboard.20140120.xlsx >> >> There are still enablers with nothing scheduled for the current timeframes >> >> *Security*: Items: 43 = 0 Epics, 20 Features, 1 User stories, 22 Work >> items, 0 Bugs >> >> https://forge.fi-ware.eu/docman/view.php/27/3306/FIWARE.backlog.security.dashboard.20140120.xlsx >> >> There are still enablers with nothing scheduled for the current timeframes >> >> *MiWi*: Items: Items: 34 = 0 Epics, 34 Features, 0 User stories, 0 Work >> items, 0 Bugs >> >> https://forge.fi-ware.eu/docman/view.php/27/3305/FIWARE.backlog.miwi.dashboard.20140120.xlsx >> >> There are still enablers with nothing scheduled for the current timeframes >> >> There’s nothing scheduled for the current sprint since everything >> scheduled are features. >> >> I’m expecting content in backlogs whose GEI’s are declared active. If >> they had changed the status to on-hold or closed, please, let me know to >> update them – and avoid non necessary concern. >> >> Thanks all for cooperation!! >> >> Kind regards, >> >> Manuel >> >> ---------------------------- >> >> Manuel Escriche Vicente >> Agile Project Manager/Leader >> >> FI-WAREInitiative >> 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 >> >> -- >> >> ------------------------------------------------------------------------- >> Deutsches Forschungszentrum für Künstliche Intelligenz (DFKI) GmbH >> Trippstadter Strasse 122, D-67663 Kaiserslautern >> >> Geschäftsführung: >> Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) >> Dr. Walter Olthoff >> Vorsitzender des Aufsichtsrats: >> Prof. Dr. h.c. Hans A. Aukes >> >> Sitz der Gesellschaft: Kaiserslautern (HRB 2313) >> USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 >> --------------------------------------------------------------------------- >> >> >> <Nachrichtenteil als Anhang.txt><slusallek.vcf>_______________________________________________ >> Fiware-miwi mailing list >> Fiware-miwi at lists.fi-ware.eu >> https://lists.fi-ware.eu/listinfo/fiware-miwi > -- ------------------------------------------------------------------------- Deutsches Forschungszentrum für Künstliche Intelligenz (DFKI) GmbH Trippstadter Strasse 122, D-67663 Kaiserslautern Geschäftsführung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Sitz der Gesellschaft: Kaiserslautern (HRB 2313) USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 --------------------------------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-miwi/attachments/20140120/0c8d969a/attachment.vcf>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy