...
Text written with Italic blue letters explains the purpose of the field and should be deleted when this template is populated for a specific pilot.
Name: Consolidated Connection Service
The name of the pilot.
Start Date: 1. 1. 2018
The date when the pilot should start.
End Date:
The expected end date of the pilot.
Pilot Description:
Description of the pilot - what will be tested, why, how.Who leads the pilot, who participates in the pilot, who provides support,.... - list all parties involved.
...
Is this a pilot of a technology or a service. Delete what is not applicable. If it is both, then both aspects should we defined separately: objectives, means of verification, documentation etc.
Required Infrastructure:
Description of the infrastructure that will be used for the pilot. Explain also who runs which part of the infrastructure, who is responsible, contact details for the operations and maintenance team.
Users:
Who are the target users for this pilot, and who actually participates in the pilot as the user.
Objectives:
Explain the objectives for the pilot - what does the pilot want to test / prove. Define Critical Success Factors (CSFs) and Key Performance Indicators (KPIs)
Means of verification:
How it will be checked if the pilot has met the defined objectives. Consider also conducting a survey among pilot participants. Each objective might have their own means of verification. Since this page will be used for pilot closure, the table is created with the third column stating is the objective is verified and reached or not. This should be populated before the end of the pilot and be used for pilot success assessment.
| Objective | Means of verification | Status (objective verified?) |
|---|---|---|
Communication plan:
Explain how will the team communicate with pilot participants, e.g. regular (weekly/bi-weekly/...) meetings, mailing lists, instant-messaging channels,...
Additional documentation:
Provide (links to) any additional documentation as needed.
...