WP5 Kick-off meeting

03/10/2013 11:00-12:00 CEST (GMT +2:00)

Participants

FOKUS: Excused (public holiday)
CGI: Beatriz Acosta, Susana Ortega, Claudia Villalonga (organizer)
NTUA: Iosif Alvertis
Betapond: Philip O’Brien
Ambiesense: Ayse Goker, Hans Myrhaug, Juan David Millan
Velti: Timotheos Kastrinogiannis
WIT: Dónal McCarthy

Agenda

1. Welcome and WP5 presentation
2. Work Distribution: SE Allocation & Missing aspects
3. Core platform components required by the SE
4. AOB

1. Welcome and WP5 presentation

CGI shortly presents the WP5.

2. Work Distribution: SE allocation & Missing aspects

After some discussion there is a first WP5 agreement on the SE distribution among tasks and partners (FOKUS role should still be clarified):

One might think that the number of SE is unbiased among tasks. However, all the items described in the DoW for T5.2 might be covered by the current SE, whereas for T5.1 and T5.3 new SE might need to be defined for the second iteration. Therefore, maybe at this moment there is not balance, but there will be at the end of the project. The missing features described in the DoW but not covered at this moment will have to be clarified later on.

It is agreed that each SE will have one responsible and contributors which will work in teams and organize their own meetings independently of the tasks. The SE responsible will report about the SE implementation evolution to the corresponding task leader and WP leader in the WP5 regular meetings. This way, the workload will be distributed as equally as possible among partners, tasks and SEs, avoiding the management overhead for T5.2 which has assigned four SE.

Velti requests to present to the project management the proposal of SE’s allocation and SE-centric way of working in order to get their approval to implement this approach in WP5.

3. Core platform components required by the SE

This agenda item is not discussed during the meeting, it is only shortly presented.
The core platform functionalities necessary towards the implementation of each SE should be identified. The goal is that WP4 work could be prioritized in order to assure that WP5 has the means to start working as soon as possible.
It is decided that each SE responsible will identify the core platform functionalities necessary towards the implementation of each SE. This list will be discussed with WP4 during the next WP4-WP5 meeting.

4. AOB

Once the open issues are clarified, it should be decided about regular WP meetings.

Action points