Pilot Procedures
Back to main page of D4.7 Initial Running Phase Report
Back to previous Chapter: 3. Goals and Success Criteria
4.1 End users engagement progress and dissemination/impact activities
Description of the way end users were recruited and involved. Use D4.6 section 4.1 (User Involvement) as a basis.
- Matrix of which DE/DO combination will work with which kind of users (focus groups).
- Rough planning for user involvement (start recruiting 2,5 months prior to start of pilot)
- Recruit startups (AT) and self-employed experts from the professional network of DBA partners
- set up microsite, that provides an animation (explanatory/promotional video) and information on the pilot, as well as how to get involved.
- Intention of EuroChambers meeting?
4.2 Pilot governance and internal progress reporting
Description on how the pilot governance was executed compared to how it was planned. Use D4.6 section 7 (Running Phase Management Plan) and section 7.5 (Governance) as a basis.
4.3 Knowledge exchange among pilot partners (Wiki…)
Description of the way DBA pilot partners exchanged knowledge that they gained from running the pilot
- In several cases, the pilot running (registration process) was done in a Teams meeting, where the representative and a DBA team member attended. The DBA remember recorded the registration steps done by the representative. Immediately afterwards, the meeting was used to fill in the questionnaire and discuss the experience of the representative at the same time, allowing for an efficient involvement of the representative while still being able to collect highly qualitative information to evaluate.
- After the pilt runs and collection of information (questionnaires/interviews) the DBA partners met to discuss and evaluate their observations, the input from representatives and the lessons learned to process in deliverable D4.7
4.4 Stabilisation of pilot experience and user support
During piloting we might need to change things to make things works. Could be short, if any.
4.5 Planned improvement following received feedback
DBA will describe 1st iteration functionality that could be improved but these functional improvements will not be implemented in the 2nd iteration (because the 2nd iteration focusus on new, different functionality). The functional improvements are recorded for future use, outside of the pilot. Other improvements (on procedures regarding user involvement for example) can be mentioned as well, and can be implemented in the 2nd iteration.