OBJECTIVES

Objective 1.1

To efficiently manage the project consortium.

Objective 1.2

To ensure quality assurance methods are adopted and project goals and objectives.

Objective 1.3

To technically coordinate the project activities.

Objective 1.4

To monitor results and implement corrective measures, if needed.

Objective 1.5

To guarantee quality of planned milestones and deliverables.

TASKS

T1.1 - Administrative management (Leader: GJU. Partners: ALL)

Review of First Project Progress

Organising the kick-off meeting and deploying the managing structure, where roles and responsibilities will be defined. Working teams according to relevant work packages will be defined.

Registration of the Internet domain and start-up of the project Internet website.

Definition of the project’s logo together with brochures, flyers templates for presentations and project- related documents.

Deployment of a project communication infrastructure including virtual workspace for document sharing, a server for support of common software versioning. Communication between different partners will be fostered through regular teleconferences and through information routing via e-mail.

Deployment of a project management server, based on MS-Project or similar solution to allow access, through a protected web page, to all project partners and to the project officer.

Definition of risk plan with risk assessment, risk tracking strategies and relevant countermeasures.

Following and publishing quarterly reports for internal use.


T1.2 - Project coordination (Leader: GJU)

Supervision of activities leading to technology functionalities as planned.

Management of issues related to software licenses and/or required hardware.

Quality assurance and assessment/evaluation of technology results.

Conflict resolution.


T1.3 – Project quality control and risk management (Leader: GJU)

Development environments supporting task/bug tracking, developers’ Wiki, milestones and releases management, versioning.

Tools for synchronous/asynchronous communication, etc.

The project management portal to support management (monitor tasks progress, deadlines, risks, submission of reports, events, etc.).

The development environment will be upgraded and checked during the project lifetime. Quality management will be performed by the continuous monitoring of the development process under the supervision of the Technical and Risk Manager (TRM) who will be responsible for editing a 3-months risk analysis report.

A review-based mechanism has been set-up through the establishment of the Advisory Board and Stakeholders board as detailed within section “Project management”.

Deployment of a project management server, based on MS-Project or similar solution to allow access, through a protected web page, to all project partners and to the project officer.

Definition of risk plan with risk assessment, risk tracking strategies and relevant countermeasures.

Following and publishing quarterly reports for internal use.