...
| Main goals and project results | Definition of concepts | Responsible / Work package | Identified risks (constantly monitored) | Status Green = Progressing as planned in the modified project plan and roadmap. Yellow = Delays or deviations. Guidance needed. Red = Major challenges. Replanning needed. | Key Performance Indicators (KPI) - measurements | Done so far Monthly status update pages to be linked here: PMC May 6th PMC June 3rd | To be done | Deployment | Communication and dissemination of activities | Deliverables across timeline | Evaluation | ||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Framework architecture Main architecture aspects and system requirements Ecosystem and modules user scenarios | T1.1 Framework architecture design T1.2: Personal learner plan and user scenarios | WP2
Deployment WP4
| International deployment: "To tailor the functionality of this framework so that it´s suitable across Europe" (Annex I p.3)
| Deployment progress monitoring
| System requirements | Deliverable 25 Technical documentation, including glossary, model and architecture | Del 27 Pilot deployment of the architecture | M17-M22 April-September | Deliverable 18 Detailed description of the user scenarios with guidelines and advice for developers in WP3 Deliverable 21 Feedback and specifications to user scenarios Del 30 Report on pilot deployment of the architecture | Impact evaluation study | |||
Analytics prototype
| Competence visualisation based on desk research (literature) and reference group generated ideas in workshops Definition of data sources and Integration of in and outputs to the competence mapping Educations recommendation desk research (literature) | WP2 TF-LEA
Deployment WP4
| Multi-sight development work can be challenging, and can slow down velocity. This needs to be mitigated through active communications and co-working in joint location when ever possible. | Development progress monitoring
Deployment progress monitoring
| Progression plan for the CompLeap prototype | Pilot deployment of analytics prototype | National deployment (Finland - all prototypes) Detailed plan of the piloting and deployment of the analytics prototype | Deliverable 28 Pilot deployment of analytics prototype | |||||
Learner plan prototype incl 3 modules
| Three prototypes defined as:
| WP3
Deployment WP4
| The timetable for development work is very challenging and anything arising from outside of the current prioritization risks current scope of delivery. Strict timetable hinders ability to take on user feedback in development work. This needs to be documented well for future work. Many stakeholders with sometimes contradictory demands. Piloting and development planned in different organisations needs requires strong coordination of expectations on each side. | Development progress
Deployment progress
| Work started Feb 2019. | Developing and releasing the initial version of the Beta prototype (Beta part 1) by Month 18 and the full Beta version (Beta part 2) by Month 22); Progression plan for the CompLeap prototype Implemented by the 30th of May 2019 Competence Profile
Recommended educational offer
Recommendation system needs for analytics and algorithm availability | Developing and releasing the initial version of the Beta prototype (Beta part 1) by Month 18 and the full Beta version (Beta part 2) by Month 22); Finalised functionalities by 30th of August The user piloting of the prototypes begins in May. Improvements to usability and tweaks based on feedback received in piloting are implemented by the 30th of August. Additionally, the possibility for the learner to include their Europass as well as Open Badges will be implemented in this stage. | Online Demos for the prototype development will be held every two weeks from March 2019. | National deployment (Finland - all prototypes) Detailed plan of piloting and deploying the learner plan prototype | Communication calendar and stakeholder management | Deliverable 24 Open source code for all components, including example code Deliverable 26 Three prototypes (modules) Deliverable 29 Pilot deployment of learner plan prototype | ||
| Case Study with Europass | WP5 DUO / EDUFI | Willingness of Europass to cooperate? What's in it for them? | Workshop(s) organised succesfully in Compleap - Europass collaboration | Europass Conference in June in Budapest | Organise a workshop to share how CL is developed? | ||||||||
| Engaging communications of project results | DUO all contribution | where is the data stored? | Measurable data about the efficiency of communication
| Event Calendar | Feedback from Demo's? Number of visitors workshops? Where to store this information? | ||||||||
Effective management of project | CSC | Deliverable 14: Risk management plan - re-submitted by March 14th D14 should be resubmitted and include a contingency plan to mitigate the delays in WP3 and reach the stated project objectives. | Monthly financial reporting and monitoring in monthly project management committee meetings
| "Living documents" – reference to the Grant Agreement – Description of the Action, table 2) Deliverables, page 23: Deliverables with an open "Delivery date", for example: M6-M18:, the draft deliverable should be uploaded on the Eduuni workspace and updated regularly. Submission to the EC in the last due month. | CSC
EDUFI
Gradia
DUO
| ||||||||
...