[Fiware-iot] Priority WorkItems for S3.2.1 sprint backlog

[t.elsaleh at surrey.ac.uk]

Hello Thierry,

In the case where a workitem/feature/story spans over one sprint. How would this be registered in the backlog?

Best regards,
Tarek



From: thierry.nagellen at orange.com [mailto:thierry.nagellen at orange.com]
Sent: 09 October 2013 14:52
To: Elsaleh T Mr (Electronic Eng)
Cc: fiware-iot at lists.fi-ware.eu
Subject: RE: Priority WorkItems for S3.2.1 sprint backlog

Hi Tarek

Yes it is fine.

BR
Thierry

De : t.elsaleh at surrey.ac.uk [mailto:t.elsaleh at surrey.ac.uk]
Envoyé : mercredi 9 octobre 2013 15:51
À : NAGELLEN Thierry IMT/OLPS
Cc : fiware-iot at lists.fi-ware.eu
Objet : RE: Priority WorkItems for S3.2.1 sprint backlog

Hello Thierry,

Just to confirm that I will change the name of the features in the tracker for "IoT Discovery" to start with:

FIWARE.Feature.IoT.BackendConfManager.IoTDiscovery.{feature name}...

I hope this is acceptable.

Best regards,
Tarek

From: fiware-iot-bounces at lists.fi-ware.eu<mailto:fiware-iot-bounces at lists.fi-ware.eu> [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of thierry.nagellen at orange.com<mailto:thierry.nagellen at orange.com>
Sent: 01 October 2013 07:04
To: fiware-iot at lists.fi-ware.eu<mailto:fiware-iot at lists.fi-ware.eu>
Subject: [Fiware-iot] TR: Priority WorkItems for S3.2.1 sprint backlog

Hi all,

I'm trying to solve many issues in the backlog directly without to bother you. Some of the issues are related to previous architectures and some GEs which do not exist anymore but some other are also related to some basic rules I would remind you:

·         EPIC: do not need a release or a sprint number

·         Feature: need only a release number

·         Story: we have to create story as a fine grain of feature and then Story requires release and sprint numbers

·         Workitems: for everything we do which are not directly related to the Story development we have to create a workitem (update on documentation for a sprint, testbed activities, catalogue update, eLearning courses, specific technical work as JSON for NGSI, and so on...)

I'm working also with Manuel on GE names and GE instances. So I will come back to you as soon as this part will be solved.

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 30 septembre 2013 17:13
À : fiware-ge-owners at lists.fi-ware.eu<mailto:fiware-ge-owners at lists.fi-ware.eu>; fiware-wpl at lists.fi-ware.eu<mailto:fiware-wpl at lists.fi-ware.eu>
Cc : fiware-wpa at lists.fi-ware.eu<mailto:fiware-wpa at lists.fi-ware.eu>
Objet : [Fiware-wpl] Priority WorkItems for S3.2.1 sprint backlog

Dear Partners,

In addition to the roadmap, which include development work, I need to request you to include WorkItems in your backlog for the following themes:

*         Work done in the Catalogue

*         Documentation pending from release 2, I know it has been rejected after the under_verification step according to the comments received in the management board.

*         Work done to  fix the backlog

Please, be aware I'll be checking these items specifically during the sprint planning session, and they will be followed by the corresponding managers or stakeholders.

If the WP Leaders or the management board had identified other priorities, please, let me know.

If anything, please, don't hesitate to contact me.

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.

_________________________________________________________________________________________________________________________



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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20131016/836685ea/attachment.html>