[Fiware-i2nd] FIWARE WP7, creating tracker items, mapping of deliverables

[Banniza, Thomas-Rolf (Thomas-Rolf)]

Dear all,

 please find in this mail some thoughts related to Chris' proposal on Mapping CDI Tasks to Fiware Forge Tracker Items'.

In general, it is a good idea, to list all the needed steps (which all are linked with a sort of deliverable) when working on the items.

Looking on the potential amount of overhead (in particular in smaller teams working on smaller GEs), I would propose to reduce the complexity:

The 'feature' is seen as the lowest 'functional element' which can be accessed from an application or a user via the API. Due to this, we have stated earlier, that also the anticipated level of testing (in test bed) is the 'feature' level (or in first step in fact even EPIC if there is only one feature), as a consequence the proposed work items related to Specification, Design, TestPlan, UnitTestImplementation and ProgrammersGuideAndInstallation should also be on the 'feature' level.

One might argue, that each use story will contribute to these deliverables on feature level (collecting all the contributions of the use stories belonging to a feature), so consequently each use story should have such related work items. But this will only produce more entries in the tracker, no additional information! As a feature should only be closed if all related use stories and work items are closed, in my eyes there is anyway no gap in control of completeness.

Having defined all these deliverable work items on the feature level, in my eyes all the use stories below a feature will define the implementation of the various sub features /smaller pieces of functionality). If needed or appropriate, there may be also additional work items contributing to the implementation if there contents can not be captured easily by a use story. 

So, at least for NetIC, I would like to propose the following:

Keep the mapping to the deliverables on the feature level:
feature name:
      FIWARE.Feature.(ge).(feature name)
related use stories for mapping the deliverables:
      FIWARE.Story.(ge).CDI.DeviceSensors.GeoLocation
      FIWARE.WorkItem.(ge).(feature name).Specification
      FIWARE.WorkItem.(ge).(feature name).Design
      FIWARE.WorkItem.(ge).(feature name).TestPlan
      FIWARE.WorkItem.(ge).(feature name).UnitTestImplementation
      FIWARE.WorkItem.(ge).(feature name).ProgrammersGuideAndInstallationHelp

We should add these work items to the tracker, they will be worked on during runtime of the feature implementation.
 
What do you think about this?

Best regards and have a fine weekend,
Thomas






++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
       
 Thomas R. Banniza
 Alcatel-Lucent Deutschland AG
 Bell Labs Germany 
 Dept. ZFZ/N
                       
 Lorenzstrasse 10
 70435 Stuttgart, Germany

 Phone:   +49 711 821-32232
 Fax:     +49 711 821-32185

 email:   Thomas-Rolf.Banniza at alcatel-lucent.com
 Web:     www.alcatel-lucent.com

 Alcatel-Lucent Deutschland AG
 Sitz der Gesellschaft: Stuttgart · Amtsgericht Stuttgart HRB 4026
 Vorsitzender des Aufsichtsrates: Michael Oppenhoff  
 Vorstand:  Wilhelm Dresselhaus (Vorsitzender) · Hans-Jörg Daub ·   
            Dr. Rainer Fechner · Andreas Gehe
 
 Alcatel-Lucent Deutschland AG
 Domicile of the Company: Stuttgart · Local Court Stuttgart HRB 4026
 Chairman of the Supervisory Board: Michael Oppenhoff
 Board of Management: Wilhelm Dresselhaus (Chairman) · Hans-Jörg Daub
                      Dr. Rainer Fechner · Andreas Gehe
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
          Alcatel-Lucent : At the Speed of Ideas
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 
Diese E-Mail-Nachricht und ihre etwaigen Anlagen können vertrauliche Informationen 
enthalten. Wenn Sie diese E-Mail-Nachricht irrtümlich erhalten haben, bitten wir Sie, 
uns dies mitzuteilen und die E-Mail und ihre etwaigen Anlagen sowie etwa hiervon 
gefertigte Kopien umgehend zu vernichten. Die irrtümlich erhaltene E-Mail und 
ihre etwaigen Anlagen dürfen weder weitergeleitet noch anderweitig verwendet werden. 

This e-mail and its attachments, if any, may contain confidential information. 
If you have received this e-mail in error, please notify us and delete or destroy 
the e-mail and its attachments, if any, immediately. If you have received this e-mail 
in error, you must not forward or make use of the e-mail and its attachments, if any.