Hi all,
after some discussion with Pier and Manuel, I've prepared a step-by-step instructions for the definition of Epics/Features, Technical Roadmap for Forge and Jira:
1. Prepare a list of Epics and Features. Epics and Features usage is explained in the FI-WARE_Agile_Development_Methodology<https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Agile_Development_Methodology> page; here is a summary of rules:
* a Feature is functionality developed at most within a product Minor Release, i.e. expected to be developed in 1 to 3 months at specific dates (3 months == 3 Sprints == 1 Minor Release). Minor Release 4.1 ends in Dec 2014
* An Epic contains at least one Feature and defines a higher functionality that is not affordable in a Minor Release (i.e. 3 months at specific dates).
* Activities affordable inside 1 Sprint (1 month) are User Stories and represent a further split of one Feature; they are documented as issues in JIRA (as Features and Epics) but are not shown in Technical Roadmap or other FIWARE Forge wiki pages.
* Please note that Sprints and Release numbering are defined in this Sprints calendar<https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates>
1. Login to the FIWARE Forge site<https://forge.fi-ware.org/account/login.php?return_to=%2F> and add your Epics/Features list in this Materializing I2ND<https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_the_Interface_to_Networks_and_Devices_%28I2ND%29_in_FI-WARE_Temp> page (in this special page already added stub sections for the NEW GEris) , taking as example the Epics and Features already available in the page.
Use the following hierarchical naming convention for Features and Epics:
* FIWARE.Epic.I2ND.<GEri Name>.<Epic name>
* FIWARE.Feature.I2ND. <GEriName>.<EpicName>.<FeatureName>
Where <GEri Name> is the Component name, i.e. SDNSDK, KIARA, OFNIC or ROBOTICS for the Robotics Component.
If you have sub-components, e.g FIROS and RCM in ROBOTICS, I'd suggest to use them as a prefix in the Epic name, for instance FIWARE.Epic.I2ND.ROBOTICS.RCMPlatformCommands
Please use only letters and numbers (No symbols and no spaces! The char '.' is reserved as delimiter) and consider them Case Sensistive.
CamelCase is allowed, but not spaces, e.g. "FIWARE.Feature.Data.OrionContextBroker.PayloadParse.JSONSupport"
Please, remember to enclose Features/Epics in double squared brackets according to the mediawiki syntax (e.g. [[FIWARE.Epic.I2ND.CDI.QoE]] ) to create links to Features/Epics description pages.
1. Create Wiki pages to describe all your Epics and Features by clicking on the links of your Features/Epics in the Materializing I2ND<https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_the_Interface_to_Networks_and_Devices_%28I2ND%29_in_FI-WARE_Temp> page created at point 2.
You can now edit the content of the page created at previous point. Copy the content from Feature Example Wiki page<https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.I2ND.COMPONENTNAME.EpicName.FeatureName> (in editing mode, copy anything from this page and paste it in your page in edit mode) and change the text accordingly to describe the new Epic/Feature. Note that componentname should be replaced by the GEri name (SDNSDK, KIARA, OFNIC, ROBOTICS).
Remember to change the text for the Goal (what you intend to reach concisely, 10 words min), Description (how the goal is implemented, 30 words min), Rational (why there is a need of it, 20 words min) fields. Overall MAX number of words must be < 250.
1. In the I2ND Tech Roadmap<http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Advanced_middleware,_Interface_to_Networks_and_Robotics> wiki page describe your GEri in the "Fourth Release" section, then populate the table with the Epics and Features expected.
Please, consider all Epics and Features expected from October 2014 to September 2015 (4th Major Release).
Use the Epics/Features names (that link to wiki pages) defined at previous points 2 and 3 and follow the examples in this page for the Third Release.
1. Login to JIRA FIWARE<http://jira.fi-ware.org/secure/Dashboard.jspa> and add issues for all Epics and Feature defined at previous points; paste in the issue description (as a plain text comment) the text of the Goal, Description, Rational.
You can take as example this issue prepared for a feature of Orion Context Broker:
* http://jira.fi-ware.org/browse/DATA-162?jql=project%20%3D%20DATA
Best,
Gianmario
------------------------------------------------------------------------------------
Telecom Italia
Gianmario Bollano
Innovation - Mobile Devices & Sim Applications
Via Reiss Romoli, n° 274
Cap 10151 Torino
Phone 011 228 7103
Cell Phone 3316015048
6. WARE_Agile_Development_Methodology page; here is a summary of rules:
· a Feature is functionality developed at most within a product Minor Release, i.e. expected to be developed in 1 to 3 months at specific dates (3 months == 3 Sprints == 1 Minor Release).
· An Epic contains at least one Feature and defines a higher functionality that is not affordable in a Minor Release (i.e. 3 months at specific dates).
· Activities affordable inside 1 Sprint (1 month) are User Stories and represent a further split of one Feature; they are documented as issues in JIRA (as Features and Epics) but are not shown in Technical Roadmap or other FiwareForge wiki pages.
· Please note that Sprints and Release numbering are defined in this Sprints calendar<https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates>
7. Add your Epics/Features list editing this Materializing I2ND at FIWARE Temp<https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_the_Interface_to_Networks_and_Devices_%28I2ND%29_in_FI-WARE_Temp> (this special page already contains sections for the NEW Geris) , taking as example the Epics and Features already available in the page.
Use the following naming convention for Features and Epics:
· FIWARE.Epic.I2ND.<GEri Name>.<Epic name>
· FIWARE.Feature.I2ND. <GEriName>.<EpicName>.<FeatureName>
Where <GEri Name> is the Component name, i.e. SDNSDK, KIARA, OFNIC or FIROBOTS for the Robotics Component.
Please use only letters and numbers (No symbols and no spaces! The char '.' is reserved as delimiter) and consider them Case Sensistive.
CamelCase is allowed, but not spaces, e.g. "FIWARE.Feature.Data.OrionContextBroker.PayloadParse.JSONSupport"
Please, remember to enclose Features/Epics in double squared brackets according to the mediawiki syntax (e.g. [[FIWARE.Epic.I2ND.CDI.QoE]] ) to create links to Features/Epics description pages.
8. Create Wiki pages to describe all your Epics and Features by clicking on the links of your Features/Epics in the Materializing I2ND at FIWARE Temp<https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Materializing_the_Interface_to_Networks_and_Devices_%28I2ND%29_in_FI-WARE_Temp> page created at point 2; they redirect to a new empty page with an url of this type:
http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/<Feature<http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/%3cFeature> or Epic full name>
You can now edit the content of the page created at previous point. Copy the content from Feature Example Wiki page<https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.I2ND.COMPONENTNAME.EpicName.FeatureName> (in editing mode, copy anything from this page and paste it in your page) and change the text accordingly to describe the new Epic/Feature page created at point 3. In the text example componentname identify the GEri name (SDNSDK, KIARA, OFNIC, etc).
Note you have to add your text for the Goal (what you intend to reach concisely, 10 words min), Description (how the goal is implemented, 30 words min), Rational (why there is a need of it, 20 words min) fields. Overall MAX number of words must be < 250.
9. In the I2ND Tech Roadmap<http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Advanced_middleware,_Interface_to_Networks_and_Robotics> wiki page describe your GEri in the "Fourth Release" section, then populate the table with the Epics and Features expected.
Please, consider all Epics and Features expected from October 2014 to September 2015 (4th Major Release).
Use the Epics/Features names (that link to wiki pages) defined at previous points 2. and 3 and follow the examples in this page for the Third Release.
10. Add to JIRA an issues for all Epics and Feature defined; paste in the issue description (as a plain text comment) the text of the Goal, Description, Rational. You can take as example this issue prepared for a feature of Orion:
· http://jira.fi-ware.org/browse/DATA-162?jql=project%20%3D%20DATA
Best,
Gianmario
------------------------------------------------------------------------------------
Telecom Italia
Gianmario Bollano
Innovation - Mobile Devices & Sim Applications
Via Reiss Romoli, n° 274
Cap 10151 Torino
Phone 011 228 7103
Cell Phone 3316015048
------------------------------------------------------------------------------------
Telecom Italia
Gianmario Bollano
Innovation - Mobile Devices & Sim Applications
Via Reiss Romoli, n° 274
Cap 10151 Torino
Phone 011 228 7103
Cell Phone 3316015048
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.
[rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non è necessario.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-i2nd/attachments/20141210/7df61d68/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logo Ambiente_foglia2.jpg
Type: image/jpeg
Size: 677 bytes
Desc: logo Ambiente_foglia2.jpg
URL: <https://lists.fiware.org/private/fiware-i2nd/attachments/20141210/7df61d68/attachment.jpg>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy