| Objective / Key Result | Worst (0%) | Best (100%) | Current | Progress |
|---|---|---|---|---|
Objective 1: kick-start the pilot of study-centric data | ||||
| Complete development of the Minimum Viable Product (MVP) | 55 | 112 | 112 | 100% |
| 10 reviews have had at least 50% of their analyses migrated to study-centric data to the author's satisfaction - trial data | 0 | 10 | 3 | 30% |
| 8 Cochrane reviews have started participation in the pilot (at minimum some PICO defined) - production data | 0 | 8 | 0 | 0% |
| Objective 2: pro-actively engage with stakeholders | ||||
| User reported bugs - fix turnaround time (hours from reported to released) | 72 | 10 | >72 | 0% |
| At least one user session by development team per feature during development: #feature sessions / #features | 0 | 1 | ||
| JATS turnaround time for feedback (work days) | 14 | 3 | 7 | 64% |
| Objective 3: make our product more efficient to work on | ||||
| ReviewDB - Reduce number of Java classes that have Sonarcube Cognitive Complexity >100 | 21 | 20 | 20 | 100% |
| RevMan Web - Reduce number of JS files that have Sonarcube Cognitive Complexity >60 | 20 | 19 | 21 | 0% |
| Automate a single regression test scenario and restore calculator end-to-end tests | 0 | 2 | 1 | 50% |
2019Q2 - Progress of RevMan Web development
Objective 1: kick-start the pilot of study-centric data
Implementation of study-centric data in RevMan Web is a major project for the team this year. Study-centric data will underpin integration with Covidence and is a prerequisite or enabler for a number of elements of Cochrane's Content Strategy.
Key results
- Complete development of the Minimum Viable Product (MVP) - 100% of story points completed. Baseline: 55/122. - Rebecka Hall
- 10 reviews have had at least 50% of their analyses migrated to study-centric data to the author's satisfaction - trial data. Baseline: 0/10. - Rebecka Hall
- 8 Cochrane reviews have started participation in the pilot (at minimum some PICO defined) - production data. Baseline: 0/8. - Rebecka Hall
Objective 2: pro-actively engage with stakeholders
This objective recognises that although no major development push besides study-centric data is expected this quarter, the team may still need to respond to other workstreams underway within the CET (e.g. provide expertise related to EMS or the publishing RFP). JATS is called out specifically as a critical project (enabler for targets 1, 3, 5 and relevant to the publishing RFP) where Wiley is expected to be the driver in the coming quarter.
Key results
- User reported bugs - fix turnaround time (hours from reported to released) [72h-10h] => 0.7=28.6h. Baseline unknown. - Unknown User
- At least one user session by development team per feature during development: #feature sessions / #features. Baseline 0. - Unknown User
- JATS turnaround time for feedback (days) [14d-3d] => 0.7=6.3d. Baseline unknown. - Rasmus Moustgaard
Objective 3: make our product more efficient to work on
Quality aspects such as design and test coverage continue to be "hot topics" within the team. Certainly there is potential to increase productivity by reducing technical debt and replacing manual testing by more automation.
Key result
- ReviewDB - Reduce number of Java classes that have Sonarcube Cognitive Complexity >100. Baseline 21, goal to reduce by 1 - Federico Conte
- RevMan Web - Reduce number of JS files that have Sonarcube Cognitive Complexity >60. Baseline 20, goal to reduce by 1 - Federico Conte
- Automate a single regression test scenario and restore calculator end-to-end tests. Baseline 0/2. - Luise Ravnskjaer
Tools
Calculating progress and generating progress chart: okr-chart.xlsx
Report 28 June
Report 14 June
| Objective / Key Result | Worst (0%) | Best (100%) | Current | Progress |
|---|---|---|---|---|
Objective 1: kick-start the pilot of study-centric data | ||||
| Complete development of the Minimum Viable Product (MVP) | 55 | 112 | 112 | 100% |
| 10 reviews have had at least 50% of their analyses migrated to study-centric data to the author's satisfaction - trial data | 0 | 10 | 2 | 20% |
| 8 Cochrane reviews have started participation in the pilot (at minimum some PICO defined) - production data | 0 | 8 | 0 | 0% |
| Objective 2: pro-actively engage with stakeholders | ||||
| User reported bugs - fix turnaround time (hours from reported to released) | 72 | 10 | >72 | 0% |
| At least one user session by development team per feature during development: #feature sessions / #features | 0 | 1 | ||
| JATS turnaround time for feedback (work days) | 14 | 3 | 7 | 64% |
| Objective 3: make our product more efficient to work on | ||||
| ReviewDB - Reduce number of Java classes that have Sonarcube Cognitive Complexity >100 | 21 | 20 | 20 | 100% |
| RevMan Web - Reduce number of JS files that have Sonarcube Cognitive Complexity >60 | 20 | 19 | 21 | 0% |
| Automate a single regression test scenario and restore calculator end-to-end tests | 0 | 2 | 1 | 50% |
Report 3 June
| Objective / Key Result | Worst (0%) | Best (100%) | Current | Progress |
|---|---|---|---|---|
Objective 1: kick-start the pilot of study-centric data | ||||
| Complete development of the Minimum Viable Product (MVP) | 55 | 112 | 112 | 100% |
| 10 reviews have had at least 50% of their analyses migrated to study-centric data to the author's satisfaction - trial data | 0 | 10 | 2 | 20% |
| 8 Cochrane reviews have started participation in the pilot (at minimum some PICO defined) - production data | 0 | 8 | 0 | 0% |
| Objective 2: pro-actively engage with stakeholders | ||||
| User reported bugs - fix turnaround time (hours from reported to released) | ||||
| At least one user session by development team per feature during development: #feature sessions / #features | ||||
| JATS turnaround time for feedback (work days) | 14 | 3 | 7 | 64% |
| Objective 3: make our product more efficient to work on | ||||
| ReviewDB - Reduce number of Java classes that have Sonarcube Cognitive Complexity >100 | 21 | 20 | 20 | 100% |
| RevMan Web - Reduce number of JS files that have Sonarcube Cognitive Complexity >60 | 20 | 19 | 21 | 0% |
| Automate a single regression test scenario and restore calculator end-to-end tests | 0 | 2 | 1 | 50% |
Report 17 May
| Objective / Key Result | Worst (0%) | Best (100%) | Current | Progress |
|---|---|---|---|---|
Objective 1: kick-start the pilot of study-centric data | ||||
| Complete development of the Minimum Viable Product (MVP) | 55 | 112 | 102 | 83% |
| 10 reviews have had at least 50% of their analyses migrated to study-centric data to the author's satisfaction - trial data | 0 | 10 | 1 | 10% |
| 8 Cochrane reviews have started participation in the pilot (at minimum some PICO defined) - production data | 0 | 8 | 0 | 0% |
| Objective 2: pro-actively engage with stakeholders | ||||
| User reported bugs - fix turnaround time (hours from reported to released) | ||||
| At least one user session by development team per feature during development: #feature sessions / #features | ||||
| JATS turnaround time for feedback (work days) | 14 | 3 | 7 | 64% |
| Objective 3: make our product more efficient to work on | ||||
| ReviewDB - Reduce number of Java classes that have Sonarcube Cognitive Complexity >100 | 21 | 20 | 20 | 100% |
| RevMan Web - Reduce number of JS files that have Sonarcube Cognitive Complexity >60 | 20 | 19 | 22 | 0% |
| Automate a single regression test scenario and restore calculator end-to-end tests | 0 | 2 | 1 | 50% |
Report 3 May
| Objective / Key Result | Worst (0%) | Best (100%) | Current | Progress |
|---|---|---|---|---|
Objective 1: kick-start the pilot of study-centric data | ||||
| Complete development of the Minimum Viable Product (MVP) | 55 | 135 | 89 | 43% |
| 10 reviews have had at least 50% of their analyses migrated to study-centric data to the author's satisfaction - trial data | 0 | 10 | 1 | 10% |
| 8 Cochrane reviews have started participation in the pilot (at minimum some PICO defined) - production data | 0 | 8 | 0 | 0% |
| Objective 2: pro-actively engage with stakeholders | ||||
| User reported bugs - fix turnaround time (hours from reported to released) | 72 | 10 | N/A | 100% |
| At least one user session by development team per feature during development: #feature sessions / #features | 0 | 1 | 4/2 | 100% |
| JATS turnaround time for feedback (work days) | 14 | 3 | 7 | 64% |
| Objective 3: make our product more efficient to work on | ||||
| ReviewDB - Reduce number of Java classes that have Sonarcube Cognitive Complexity >100 | 21 | 20 | 20 | 100% |
| RevMan Web - Reduce number of JS files that have Sonarcube Cognitive Complexity >60 | 20 | 19 | 22 | 0% |
| Automate a single regression test scenario and restore calculator end-to-end tests | 0 | 2 | 1 | 50% |
Report 5 April
| Objective / Key Result | Worst (0%) | Best (100%) | Current | Progress |
|---|---|---|---|---|
Objective 1: kick-start the pilot of study-centric data | ||||
| Complete development of the Minimum Viable Product (MVP) | 55 | 122 | 63 | 12% |
| 10 reviews have had at least 50% of their analyses migrated to study-centric data to the author's satisfaction - trial data | 0 | 0 | 0 | 0% |
| 8 Cochrane reviews have started participation in the pilot (at minimum some PICO defined) - production data | 0 | 8 | 0 | 0% |
| Objective 2: pro-actively engage with stakeholders | ||||
| User reported bugs - fix turnaround time (hours from reported to released) | 72 | 10 | N/A | N/A |
| At least one user session by development team per feature during development: #feature sessions / #features | 0 | 1 | 2/1 | 100% |
| JATS turnaround time for feedback (work days) | 14 | 3 | N/A | N/A |
| Objective 3: make our product more efficient to work on | ||||
| ReviewDB - Reduce number of Java classes that have Sonarcube Cognitive Complexity >100 | 21 | 20 | 21 | 0% |
| RevMan Web - Reduce number of JS files that have Sonarcube Cognitive Complexity >60 | 20 | 19 | 20 | 0% |
| Automate a single regression test scenario and restore calculator end-to-end tests | 0 | 2 | 0 | 0% |