Instructions
Tabulate to Table 3.2a the go/no-go decision points into a Milestones table. These points can also be guidance points, such as materials ready to be delivered between Work Packages, etc. A project should not have too many milestones and they should be clear decision points that are reached after a significant amount of work is concluded to see if the planned activities are still the best way forward. Milestones are used by both the project partners and the Commission to ensure efficient monitoring of the project’s progress.
You should show how you will confirm that the milestone has been attained. Refer to indicators if appropriate. For example: a laboratory prototype that is ‘up and running’; software released and validated by a user group; field survey complete and data quality validated.
Example
|
MS # |
Milestone name |
Related WP(s) |
Due date (in month) |
Means of verification |
|
1 |
WIDGET sensor pilot model ready |
1, 3, 4 |
M12 |
Sensor completed with full tests. Ready for simulation pilot. |
|
2 |
WIDGET Software and Hardware integrated |
1, 2, 3, 4 |
M26 |
Integration successfully completed without major bugs reported. Product ready for real world pilot test. |
|
… |
Etc… |
|
|
|