[Fiware-i2nd] R: R: Synchronisation I2ND tracker - materialising wiki

[Garino Pierangelo]

Hi Andrea,

please find my answers below in your mail.
I take the opportunity to forward the mail to the whole chapter Team, as the comments might be useful for them too.

BR
Pier


Da: Andrea Simeoni [mailto:asimeoni at dis.uniroma1.it]
Inviato: mercoledì 12 settembre 2012 10:44
A: Garino Pierangelo
Cc: chris.woods at intel.com; Bollano Gianmario; Frank Schulze; vincenzo.suraci at dis.uniroma1.it
Oggetto: Re: R: Synchronisation I2ND tracker - materialising wiki

Hi Pier,

Thank you for doing this. I have some questions:

1. If I add a User-Story in the tracker, should I do the same in the materializing wiki?
No, this is no longer necessary: it is one the simplifications I reported in the other mail I sent yesterday to the whole I2ND Team.

2. When I add a Work-Item or a User-Story in the tracker, how are they linked to the corresponding Feature? Should I use the "Summary" box?
The naming convention for User Stories, as well as for WorkItems, is the following:

FIWARE.Story.I2ND.CDI.<EpicName>.<FeatureName>.<StoryName>

Where the EpicName, FeatureName etc correspond to the Epics/Features the User Story is associated to


FIWARE.WorkItem.I2ND[.CDI[.<EpicName>[.<FeatureName>[.<StoryName>]]]].<WorkItemName>

Where again the EpicName, FeatureName etc correspond to the Epics/Features/ User Story the WorkItem is associated to. The main difference here is that a WorkItem could be associated to any 'level of hierarchy', that is there can be a WorkItem assigned globally to CDI, or assigned to an Epic, which would result in the following examples:

FIWARE.WorkItem.I2ND.PeerReviewofCloudChapter      as it is a global task for the I2ND team  (usually these are set by WPL/WPA)

Or (as you correctly did in the past):

FIWARE.WorkItem.I2ND.CDI.QoE.Enhance Webinos integration document   (this is a workitem related to Epic QoE)


3. What about the work done in past Sprints? Do Reviewers accept what we have done so far, even if the backlog is not completely in line with their expectations?

The main objective for today is to have a clear vision of what we are doing in the current Sprint, and from now onwards (i.e. complete regularly month by month the entries).
This means that we need to concentrate on documenting properly (without excess as we defined in the call yesterday...) the 'work to be done', including all the Features we defined in the 'Materialsing' wiki.
For what concerns the past periods, it is at the moment valid to keep the situation as it was, i.e. we are not asked to add entries for all what done in the past not completely documented. On the other hand, as I2ND as particularly for CDI, we are already in a good position since many entries for past periods are already there (thanks to all of you who updated the tracker rather regularly :)

Hope this clarifies the points.

Thank you very much,
-Andrea

Il 12/09/2012 08:24, Garino Pierangelo ha scritto:
Hi All,

the new features concerning the CDI are present in the tracker, IDs from 2570 to 2584.

You should find in the 'Power query' pull-down menu an entry 'Most  Recent Tickets' which shows the tickets from the latest ID to the oldest one, please tell me if you don't see that query in the list.

Each ticket has been assigned to one of us, but it is still open. I leave to you the task of:

1-      Setting your assigned tickets 'Under execution' for those Features you're currently working on

2-      Defining and entering User Stories tickets to further split the programming development to be done for those Features (for the time being just put User Stories for those Features you're actually working on now). If case a Feature is self-contained and not structured, a single User Story could be created for that Feature (try to limit this situation to few cases)

3-      Assigning those User Stories you're working on in this Sprint the ReleaseID and SprintID.

When the list of WorkItems Chris is going to introduce is complete (thanks Chris for taking this in charge!), we'll have the whole list of actions we're performing in this Sprint, as requested.
BR
Pier




Da: Garino Pierangelo
Inviato: martedì 11 settembre 2012 17:15
A: chris.woods at intel.com<mailto:chris.woods at intel.com>; Andrea Simeoni (asimeoni at dis.uniroma1.it<mailto:asimeoni at dis.uniroma1.it>); Bollano Gianmario; Frank Schulze; vincenzo.suraci at dis.uniroma1.it<mailto:vincenzo.suraci at dis.uniroma1.it>
Oggetto: Synchronisation I2ND tracker - materialising wiki

Hi All,

as planned I'm doing the alignment of I2ND tracker for those entries (Epics/Features) currently present in the 'Materialising' wiki page.
>From what it results, I found a number of things to be done, I'll personally do most of them, but for a few others I need your help to understand the reason of misalignment (it could just be a matter of naming).
Here is the list:

Missing in tracker: (Pier's going to add all of them):

 *   FIWARE.Feature.I2ND.CDI.QoE.Feedback<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.I2ND.CDI.QoE.Feedback>
 *   FIWARE.Feature.I2ND.CDI.QoE.Context<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.I2ND.CDI.QoE.Context>
 *   FIWARE.Feature.I2ND.CDI.QoE.Controller<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.I2ND.CDI.QoE.Controller>
 *   FIWARE.Feature.I2ND.CDI.QoE.QosEngine<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.I2ND.CDI.QoE.QosEngine>
 *   FIWARE.Feature.I2ND.CDI.QoE.APIHandler<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.I2ND.CDI.QoE.APIHandler>

*  FIWARE.Feature.I2ND.CDI.Phone.PhoneInterfaceAvailability<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.I2ND.CDI.Phone.PhoneInterfaceAvailability>

 *   FIWARE.Feature.I2ND.CDI.DeviceConnectivity.MobilityManagerProfileInterface<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.I2ND.CDI.DeviceConnectivity.MobilityManagerProfileInterface>
 *   FIWARE.Feature.I2ND.CDI.DeviceConnectivity.CurrentConnectivityDetection<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.I2ND.CDI.DeviceConnectivity.CurrentConnectivityDetection>
 *   FIWARE.Feature.I2ND.CDI.DeviceConnectivity.DeviceConnectivityInterfaceAvailability<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.I2ND.CDI.DeviceConnectivity.DeviceConnectivityInterfaceAvailability>

 *   FIWARE.Feature.I2ND.CDI.DeviceConnectivity.APIHandler<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.I2ND.CDI.DeviceConnectivity.APIHandler>
 *   FIWARE.Feature.I2ND.CDI.DeviceConnectivity.MobilityManagement<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.I2ND.CDI.DeviceConnectivity.MobilityManagement>

 *   FIWARE.Feature.I2ND.CDI.RemoteDeviceManagement.DeviceConfiguration<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.I2ND.CDI.RemoteDeviceManagement.DeviceConfiguration>
 *   FIWARE.Feature.I2ND.CDI.RemoteDeviceManagement.ApplicationManagement<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.I2ND.CDI.RemoteDeviceManagement.ApplicationManagement>
 *   FIWARE.Feature.I2ND.CDI.RemoteDeviceManagement.FirmwareUpdate<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.I2ND.CDI.RemoteDeviceManagement.FirmwareUpdate>

 *   FIWARE.Feature.I2ND.CDI.Proximity.NFC<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.I2ND.CDI.Proximity.NFC>

These tracker entries are probably to be realigned with Features in the wiki (and name made compliant with rule...): Who can tell me what to do?
FIWARE.Story.I2ND.CDI.Feature.UserProfile.SignOn<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1517&group_id=10&atid=192>
FIWARE.Story.I2ND.CDI.Feature.UserProfile.AccessToLocalAndPersonalDeviceData<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1516&group_id=10&atid=192>

Present  in tracker and not in wiki: Who can tell me what to do? Remove from tracker as no longer relevant or add to wiki Features?

FIWARE.Story.I2ND.CDI.Feature.UserProfile.Access<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1518&group_id=10&atid=192>

FIWARE.Story.I2ND.CDI.Feature.DeviceConnectivity.WiFi<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=1535&group_id=10&atid=192>
FIWARE.Feature.I2ND.CDI.DeviceFeatures.CommonDeviceInterface<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=911&group_id=10&atid=192>
FIWARE.Feature.I2ND.CDI.DeviceFeatures.CapabilityDescription<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=912&group_id=10&atid=192>



Thanks a lot for sending me your feedback asap on the latter two items :)


BR
Pier








------------------------------------------------------------------
Telecom Italia
Pierangelo Garino
Innovation & Industry Relations - Research & Prototyping
Via G. Reiss Romoli 274, I-10148 TORINO
Tel: +39 011 228 7142

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:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non è necessario.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20120912/7f423bf4/attachment.html>