-
Notifications
You must be signed in to change notification settings - Fork 0
Risks
Stefan Piatek edited this page Oct 11, 2022
·
7 revisions
| this month | last month | weeks on list | risk | risk resolution |
|---|---|---|---|---|
| 1 | 3 | 13 | FHIR data model changing | Develop FSH specification (which defines the implementation guide and profiles), review of each new bundle and base example data on fake report so only randomly generated identifiers should change |
| 2 | 1 | 13 | prototype used as production application | Can't offer support to DRE afer the end of our funding, so DPIA and ability to host clinical data needs to be in place to give time for rounds of iteration |
| 3 | 2 | 8 | GOSH deployment | May only have windows for deployment, for synthetic fhir server: have deployed on github pages. |
| 4 | 4 | 23 | creeping requirements | review of requirements every 2 weeks, order by value and push down nice to haves until all high priority issues are completed |
| 5 | 5 | 23 | released software has low quality | disciplined development practices (version control, review, tests and CI). End user sign off would be useful as well |
| 6 | 6 | 23 | no visibility on project progress | visible project board, write code in the open and under an open source license |
Stage 1
| this month | last month | weeks on list | risk | risk resolution |
|---|---|---|---|---|
| 1 | 0 | 4 | too much time spent on investigation | review work mid May to ensure a demo-able form with no frills |
| 5 | 0 | 8 | integration with fhir | straight to using fhir API rather than intermediate bundle which may not be correct |
| 6 | 4 | 15 | nothing useful released | agile development, constantly releasing usable code rather than goldplated. Would still like to have an end user of this to demo and get feedback from. Have satisfied stage 1 requirements. |
Stage 2:
| this month | last month | weeks on list | risk | risk resolution |
|---|---|---|---|---|
| 1 | 1 | 8 | Unclear what we're aiming for | Start stakeholder engagement and requirements gathering ASAP. Ideally multiple interested parties or a single user targetted. Draw up prototype wire frames and try to work through the application steps with stakeholders. |
| 2 | 2 | 4 | Not enough specification to allow developers to dedicate all their time to stage 2 | Any time where stage 2 work has not been defined will be used to work on the feature backlog for stage 1. |