[Fiware-cloud] Fw: [Fiware-wpa] IMPORTANT REMARKS regarding the FI-WARE Technical Roadmap Deliverable

[Alex Glikson]

FYI, towards the roadmap discussion tomorrow.

----- Forwarded by Alex Glikson/Haifa/IBM on 06/03/2012 10:56 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:   05/03/2012 07:19 PM
Subject:        [Fiware-wpa] IMPORTANT REMARKS regarding the FI-WARE 
Technical       Roadmap Deliverable
Sent by:        fiware-wpa-bounces at lists.fi-ware.eu



Hi all,

  I guess you are dealing with the writing of the FI-WARE Technical 
Roadmap deliverable.   I also guess that you would agree that, while the 
text we are going to produce here doesn't need to be long, it may be 
highly relevant because we are trying to fix there WHAT WE COMMIT TO 
DELIVER WHEN.   Therefore, I would like to make a couple of remarks:
Please try to commit for the first release what we believe is strictly a 
MUST, that is, things we believe that, if not brought, FI-WARE will be 
useless to the UC projects (or, at least, they will blame of us :-)   Note 
that we didn't specify what we were going to bring in the first release 
within the current signed DoW.   Therefore, nobody will be able to make 
the point that we are not fulfilling the DoW if we do not deliver this or 
that.   HOWEVER, we will JUDGED with respect to whatever we commit to 
deliver now: if we promise to deliver something in the first release now 
and then we fail to deliver it, then the reviewers will have the right to 
say we failed and reject acceptance of, among others, the FI-WARE Testbed 
deliverable.
It's not a matter of committing to deliver what we believe we can develop 
and have ready for integration by end of April based on selected baseline 
assets.   Don't underestimate the integration efforts on the testbed. Also 
don't underestimate integration coordination efforts: just following up 
that a given GE is properly installed and configured in the Testbed will 
take its time not only to leaders of tasks in WP10, but also to you as 
chapters leads and myself ... so, why should we spent time in something 
that nobody would consider urgent/must ?  It's better that we rather 
concentrate on integrating the less things possible for the first release 
and leave integration of things that can wait for later.   We should just 
focus on what can be a STABLE integrated FI-WARE Release and then make it 
grow, adding new GEs or features in already integrated GEs. 
Despite we talk just about Major Releases in the FI-WARE DoW or in the 
Technical Roadmap Deliverable, we should plan to be able to upgrade the 
testbed at our convenience every three months, so that new GE software or 
upgrades on existing GEs arrives end of July 2012, October 2012, January 
2013, Abril 2013, July 2013, ... and then new releases of the testbed are 
published by end of October 2012, January 2013, Abril 2013, July 2013, 
October 2013 respectively (we typically book three months for integration 
testing in the testbed).     So don't hesitate to defer things for the 
first or the second minor release within the second major release of 
FI-WARE in your planning. 
I propose the following to handle what is planned in the different minor 
releases of the second major release.   We will publish the Technical 
Roadmap deliverable just making the distinction on what goes in the first 
Major Release and what goes in the second Major Release of FI-WARE.    And 
please be conservative promising things for the First Major Release. Then, 
what we will do is ask the UC projects:   Is there anything planned for 
the Second Major Release you wish to have prioritized ?   Then, based on 
their feedback, we will prioritize the features they highlight and will 
try to deliver then a little bit in advance, planning them in the first 
minor releases of the second major release (e.g., to get it ready in the 
FI-WARE Testbed either by end of October 2012 or end of January 2013). 
Doing so, we are showing we care about their priorities and show some 
flexibility. 
  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-wpa mailing list
Fiware-wpa at lists.fi-ware.eu
http://lists.fi-ware.eu/listinfo/fiware-wpa
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-cloud/attachments/20120306/5b6811cf/attachment.html>