[Fiware-iot] delivery plan 2.0

[Farkas, Lorant (NSN - HU/Budapest)]

Dear All,

I need to reconsider my earlier statement: it has been decided that any
delay in the M12 deliverables related to the technical work packages (in
our case D5.1...D5.5) after 23rd of July will imply that the PM-s
according to the plan between M12 and end of July by the respective
partner will not be accepted for the respective deliverable.

Example: assuming a partner has 7.5 PM-s allocated in WP5 between 1st of
May and end of July,  and the partner commits D5.1...D5.4 on the 23rd of
July, the deliverables are accepted, but the partner fails in committing
D5.5. Then 80% of the PM-s can be accepted between May and July, that is
up to 6 PM-s.

Because of this from WPA/WPL perspective I have to ask you to
re-prioritize our activities to cover first D5.1...D5.5 now and
everything else afterwards.

This would mean we have to bring D5.5 Unit Testing Plan and Report to
W29. I am bringing also the standardization plan and reporting
contribution forward from W31 to W30 because of the high importance of
this topic.

The redesigned plan would be:

WP2 deliverables where we need to contribute:
D2.3 Architecture specifications			end of W30
D2.4 Technical roadmap					end of W31

WP5 deliverables (fully ours):
D5.1 Open Specifications				end of W28
D5.2 Software release					end of W29
D5.3 Installation and Administration guide	end of W28
D5.4 Users and Programmers guide			end of W29
D5.5 Unit Testing Plan & Report			end of W29

WP11 deliverables where we need to contribute:
D11.4 Standardization plan and Report		end of W30




_____________________________________________
From: Farkas, Lorant (NSN - HU/Budapest) 
Sent: Wednesday, July 11, 2012 2:06 PM
To: 'fiware-iot at lists.fi-ware.eu'
Subject: list of actions for the partners


Dear All,

Sorry for missing our weekly call.
Let's stay pragmatic and try to plan our activities according to my
originally proposed planning, despite what has been discussed in the
weekly call or disclosed in earlier e-mails.

Partner contribution high level plan:

WP2 deliverables where we need to contribute:
D2.3 Architecture specifications			end of W30
D2.4 Technical roadmap					end of W31

WP5 deliverables (fully ours):
D5.1 Open Specifications				end of W28
D5.2 Software release					end of W29
D5.3 Installation and Administration guide	end of W28
D5.4 Users and Programmers guide			end of W29
D5.5 Unit Testing Plan & Report			end of W30

WP11 deliverables where we need to contribute:
D11.4 Standardization plan and Report		end of W31

-For the W28 and W29 deliverables I already captured every needed action
partner by partner/person by person, it should already be in your
inboxes. Tasks incorporate detailed information on what you should do
and how. If something is not clear, please ask.
-For the W30 and W31 activities I still need to create the tasks in
forge, you will receive notifications about them.
-If you need to delegate tasks (example: Tobias delegates something to
Salvatore), please do it within the Fusion Forge task assigned to you,
or let me know by e-mail. 
-If your task progresses in some way, please write an e-mail or make a
comment in the task I assigned to you. We will in parallel monitor the
outcomes and make comments if we see progress, but it would be nice if
you do his proactively.
-Please also mark in the task the number of hours it took you/your
colleagues to finalize it, -I put an early estimate when the task was
created. It will help us to better plan in the future and to
monitor/assess the amount of work you spent on the respective task.
-If you finish something belonging to W28, please start working on tasks
belonging to W29, and so on.

Thanks & Br,

Lorant




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20120716/46078dc5/attachment.html>