-
Notifications
You must be signed in to change notification settings - Fork 1
3.1. Project structure
(Recommended length: up to 3 pages) Provide a global overview of the technical work to be performed and of the Work Breakdown Structure (work packages) envisaged towards it. Use diagrams where possible and do not hesitate to separate the hierarchical view (organisation of WPs and tasks in a tree) from the process view (e.g. interdependency between WPs, yearly processes, etc.). Explain the interfaces and interactions between work packages, and between consortium members. Justify how the project structure supports the project objectives. Do not provide detailed Work Package and Task descriptions in the Project Outline. The detailed Work Package descriptions are only requested in the Full Project Proposal and will be fully discarded for the PO evaluation: where possible, try to avoid describing task contents in a PO and focus on how the WPs relate to each other. This section should convince the reviewers that the project structure helps the consortium ac