[Fiware-cloud] Fw: [Fiware-wpl] Instructions for resubmission of FI-WARE Technical Roadmap

[Alex Glikson]

FYI

----- Forwarded by Alex Glikson/Haifa/IBM on 03/08/2012 02:00 PM -----

From:   Juanjo Hierro <jhierro at tid.es>
To:     "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>, 
Date:   03/08/2012 11:02 AM
Subject:        [Fiware-wpl] Instructions for resubmission of FI-WARE 
Technical       Roadmap
Sent by:        fiware-wpl-bounces at lists.fi-ware.eu



Dear colleagues,

  Please find here the instructions to be followed to generate a new 
version of the Technical Roadmap deliverable to be published on the public 
Wiki and be resubmitted to the EC.

  The instructions are pretty simple and the best way to explain them is 
by referring to the example I have created on the private wiki:

https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4Example_(Resubmission)_-_Reference_Example


  That example is based on the current contents of the Technical Roadmap 
linked to the Apps Chapter.    Based on that, the steps to follow are:

Update the Introduction: 
We should make a reference to contents of the FI-WARE Architecture and 
Open Specifications part of the wiki, rather than the FI-WARE Product 
Vision (at the time at which the first version of the Technical Roadmap, 
the Architecture and Open Specifications didn't exist, but this is no 
longer the case) 
You should also refer to the page dealing with Release and Sprint 
numbering, with reference to calendar dates. 
All of this may be done by simple copy&paste from the reference example. 
Description of first Major Release: 
The high-level description you had there will be kept, although I have 
introduced some minor changes in the text to refer to make it clear it was 
a high-level description (because details will follow).   Check the 
differences between the provided example and the Technical Roadmap of the 
Apps Chapter currently published on the Wiki. 
You will add a table which illustrate, one row per FI-WARE GE planned in 
the first Major Release, the features that will be supported.   The table 
shall be preceded by the paragraph: 
For a more detailed description of features provided, you can refer to the 
following table which help to identify what Backlog Features will be 
supported for each FI-WARE GE: 
You will see that table in the reference example, with the details of some 
of the FI-WARE GEs.   I have based them on info available in the public 
part of the Apps Chapter Backlog available on the  public wiki. 
Essentially, you just need to include the references to the Backlog 
Features that have been addressed in the first Release for each FI-WARE GE 
(note this list should also include Features supported by the baseline 
assets) 
When you distinguished between the delivery by end of July and by end of 
September, the above three points indeed apply per each (section for the 
release by end of July and section for the release by end of September)
Description of second Mayor Release: 
The high-level description you had there will be kept, although I have 
introduced some minor changes in the text to refer to make it clear it was 
a high-level description (because details will follow).   Check the 
differences between the provided example and the Technical Roadmap of the 
Apps Chapter currently published on the Wiki. 
You will add a table which illustrate, one row per FI-WARE GE planned in 
the first Major Release, the features that have already been planned or 
the Epics that will be analyzed and further refine which it is foreseen 
will lead to specification of Features to be planned as part of the second 
release.   The table shall be preceded by the paragraph: 
For a more detailed description of features to be provided, you can refer 
to the following table which help to identify what Backlog Features have 
already been specified and planned for the second Major Release of FI-WARE 
(and indication of the minor release is provided). The table also contain 
Epics currently under analysis which most probably will lead to the 
identification of Backlog Features to be planned also in the second Major 
Release 
You will see that table in the reference example, with the details of some 
of the FI-WARE GEs.   I have based them on info available in the public 
part of the Apps Chapter Backlog available on the  public wiki.   However, 
since there were no Backlog Features still planned, I have just created 
some fictitious features to make the reference example complete.  If a 
FI-WARE GE does have Epics, but not Features, then write down "(not yet 
specified)" in the column about Features. 
Regarding links to Features/Epics.   They should be wiki references, as 
they appear in the reference example.   No problem if they do not resolve 
in the FI-WARE Private Wiki, they should work once translated into the 
public Wiki
Description of Future Releases: 
I believe we can keep this part as it is now 

  I have prepared a section with placeholders for your contributions at:
https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.4

  Please get them ready by Tuesday 12:00pm CET.   It shouldn't be that 
difficult if you made a good exercise updating Epic/Features in the 
Backlog.
  During the rest of August, you should update the stakeholder field of 
each Epic/Feature in the backlog.    Please do it with the best of your 
knowledge.   Put "FI-WARE partners" if an Epic/Feature doesn't come from 
an UC project but was there within our original plans.    Add the name of 
a UC project if you already know they are looking for it (based, for 
example, on feedback from the educational sessions).   We will ask UC 
projects in parallel to review the Epics/Features on the wiki and add the 
name of their project in the plan to use the GE and wish to use the 
functionality linked to that Epic/Feature.
  Best regards,

-- Juanjo

-------------
Product Development and Innovation (PDI) - Telefonica Digital
website: www.tid.es
email: jhierro at tid.es
twitter: twitter.com/JuanjoHierro

FI-WARE (European Future Internet Core Platform) Chief Architect

You can follow FI-WARE at:
  website:  http://www.fi-ware.eu
  facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
  twitter:  http://twitter.com/FIware
  linkedIn: http://www.linkedin.com/groups/FIWARE-4239932



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
_______________________________________________
Fiware-wpl mailing list
Fiware-wpl at lists.fi-ware.eu
http://lists.fi-ware.eu/listinfo/fiware-wpl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-cloud/attachments/20120803/88952951/attachment.html>