Implementation Plan timeline
| Version: 1.0 | Month | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Tranche | Deliverable | Tasks | Expected effort | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 |
Leadership | Discovery landscape | Interviews/workshops with stakeholders to understand current processes, software and resources. | PM plus a facilitator if required will spend up to 20 days finding out and mapping current efforts | 1: yes | 2: no | 3: no | 4: no | 5: no | 6: no | 7: no | 8: no | 9: no | 10: no | 11: no | 12: no |
Leadership | Agree the scope | Agree who & which software will be involved in collection, aggregation and consumption. | PM will make recommendation to project board to make a decision | 1: yes | 2: no | 3: no | 4: no | 5: no | 6: no | 7: no | 8: no | 9: no | 10: no | 11: no | 12: no |
Collect & manage data | Process of collecting data | Map out the process to be used for collecting data into a single repository | Service provider/collector will submit their data in 1 day.Collectors will continue to work in the scope | 1: no | 2: yes | 3: yes | 4: yes | 5: yes | 6: yes | 7: yes | 8: yes | 9: yes | 10: yes | 11: yes | 12: yes |
Assure data quality | Repository of trusted data | Allocate service providers to a team of assurers, with guidance on how data can be trusted by consumers. | Assurer will work on initial data for 0.5 day per service provider and then 0.25 per regular assurance | 1: no | 2: no | 3: yes | 4: yes | 5: yes | 6: yes | 7: yes | 8: yes | 9: yes | 10: yes | 11: yes | 12: yes |
Publish & re-use | Aggregating into single repository | A database will be used to store all the collected data. De-duplication should be considered | Automated process will need to be set up and then used throughout project | 1: no | 2: no | 3: no | 4: yes | 5: yes | 6: yes | 7: yes | 8: yes | 9: yes | 10: yes | 11: yes | 12: yes |
Publish & re-use | Building the API | An API will be built and validated through ORUK validator | This could be purchasing a licence, re-using open source or building from scratch. Expected £10k costs. | 1: yes | 2: yes | 3: no | 4: no | 5: no | 6: no | 7: no | 8: no | 9: no | 10: no | 11: no | 12: no |
Publish & re-use | Applications showing use of collected data | The consumers will need to be able to extract appropriate data from the API and use in their process/application |
| 1: yes | 2: yes | 3: yes | 4: yes | 5: no | 6: no | 7: no | 8: no | 9: no | 10: no | 11: no | 12: no |
Publish & re-use | Applications showing use of collected data | The consumers will need to be able to extract appropriate data from the API and use in their process/application |
| 1: no | 2: no | 3: no | 4: no | 5: yes | 6: yes | 7: yes | 8: yes | 9: yes | 10: yes | 11: yes | 12: no |
Performance monitoring | Management report | Define the management data that is required including evidence for business case | Write Power BI, Tableau report using data from repository and applications | 1: no | 2: no | 3: no | 4: no | 5: no | 6: no | 7: no | 8: no | 9: no | 10: no | 11: no | 12: yes |
Project close | Recommendations for scaling | Document all lessons learned, what worked and new ideas for scaling further. Give opinion whether the business case and concept is proven. | PM to write bullet point list under main headings of Collect, Assure and Re-use to support a further scaling of the project | 1: no | 2: no | 3: no | 4: no | 5: no | 6: no | 7: no | 8: no | 9: no | 10: no | 11: no | 12: yes |