[Fiware-administrative] FI-WARE: Follow-up of effort (M16-M17)

JAVIER DE PEDRO SANCHEZ jdps at tid.es
Wed Oct 3 08:24:59 CEST 2012


Dear all,
In another particularized e-mail, I'm going to ask you to send your current effort from M16 (Aug 2012) until M17 (Sep 2012) included.
Please keep in mind that it won't include the modifications of the second amendment because we are still working on it.

In behalf of Juanjo Hierro, Technical Manager and Chief Architect of the project, I want to remind you the minute of PCC meeting about delay of some deliverables:

We have to remind that delay of some deliverables until end of June was not approved by the PO (software release, unit testing plan, accompanying guides) and they remain delayed since month 12 (end of April).
None of the partners have delivered by end of June despite this was what we committed to do with the PO when we asked for a formal re-planning.   We shouldn't go later than July 23rd.
TID proposed to impose measures that translate into rejection of costs by those partners that do not deliver by July 23rd.  This measure was already discussed at the joint WPLs/WPAs follow-up confcall held on July 9th and, at that time, TID asked to announce this to rest of partners.
Now, it is time to fix the details of what these measures will be. TID proposes the following (we will also develop a similar formula to FI-WARE GEs we commited to be available on the testbed by end of September, using September 10th instead of July 23rd):
*         Partners involved in development of a given FI-WARE GE that is not delivered by July 23rd will not be allowed to justify any PM in WP3-WP8 until they deliver.  Once they deliver, it will be assumed that the PMs consumed had been those that were reported until month 12, so that no additional PMs will be accepted.   Planning of PMs for the remaining of the project will be adjusted accordingly.
*         Delivery of software that doesn't work or proves to be rather unstable in the FI-WARE Testbed will not be considered as actually delivered.  This intends to prevent that some partner delivers software which doesn't meet enough quality by July 23rd just to avoid costs rejections.
*         Partners that deliver by July 23rd will be allowed to justify the PMs planned until July 23rd (provided that the software they have delivered is not rejected as stated in the previous point).  This means they would not suffer any impact.
*         PMs of any partner within a given WP (WP3-8) are distributed from month 10 on across deliverables as follows (note: we propose to include whatever distribution gets approved in the next amendment of the DoW):
o    Contributions to WP2 deliverables: 10%
o    FI-WARE Open Specifications: 20%
o    SW Release: 40%
o    Installation and Admin Guides: 7,5%
o    Users' and Programmers' Guides: 7,5%
o    Unit Testing Plan and Report: 15%
*         Deliverables of a given WP rejected by the WPL will be rejected. TID and the WPL agree on any amendment of the above rules that may apply (e.g., failing in delivery of a given GE may not be the fault of all partners involved in development of that GE so that they agree not to apply penalization to some partners).   TID may reject some additional deliverables if it considers that they do not meet the defined guidelines or expected quality, after discussion with the WPL.
*         Similar rules would apply to WP9 (development tools)
If you want to make modifications of declared efforts in previous months, please let me know to unlock them.

Thank in advance for your collaboration.
BR
Javier.


________________________________

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-administrative/attachments/20121003/b2a327cf/attachment.html>


More information about the Fiware-administrative mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy