2019Q3 - Progress of RevMan Web development

Overall aim: Drive adoption of RevMan Web

  • Objective 1: Remove blockers for MEs to advocate for RevMan Web
    • Process: MEs integrated in the sprint cycle (participate in prioritisation, grooming and demo) - yes/no for each activity per sprint. yes/total = score   (RH)
    • The ME Exec is satisfied with features implemented yes/number of stories (verify with ME Exec) (RH)
    • A certain weighted % of blockers stated by individual MEs has been removed - Baseline is  82/9 (total number of blockers/persons who tried RevMan Web), current = 0, 7 blockers/person=100%  (RH)
  • Objective 2: Demonstrate the added value of RevMan Web for authors
    • Ensure a succesful references-only integration with Covidence (GvV)
      • Scope and user journeys agreed by both teams
      • Scope and user journeys validated with users
      • Collaboration process and definition of done agreed by both teams
      • Breakdown into releasable chunks agreed by both teams
      • Environments set up that cover the user journeys
    • 3 new "not possible in RevMan 5" incentives for authors integrated in promotional activities (e.g. study-centric data pilot success story, covidence integration ready, new commenting system, ...) (GvV)
  • Objective 3: Go slower to go faster
    • Implement JPA relationships on domain entities in ReviewDB (0% of relationships covered) - goal 100% (JHH)
    • Reduce number of manual regression test scenarios (baseline: ?) - reduce by 70% of baseline (IWH)
    • Run a succesful team-led recruitment for 2 new team members (IWH)
Start dateNotes
1 JulHoliday - no sprint
15 JulHoliday - no sprint
29 JulSprint 1: GRADEpro integration
12 AugSprint 2: GRADEpro integration
26 AugSprint 3 Search date
9 SepSprint 4 Validation report, assessed as up-to-date
23 SepSprint 5 Validation report, Setting Q4 objectives

Report September 20th

NumberObjective / Key resultWorst (0%)Best (100%)CurrentProgress
1Remove blockers for MEs to advocate for RevMan Web



1.1MEs integrated in the sprint cycle0159/1275%
1.2ME Exec satisfied with stories implemented0100%
1.3Blockers stated by MEs have been removed9.11111179.1111110%
2Demonstrate the added value of RevMan Web for authors



2.1Ensure a succesful references-only integration with Covidence05125%
2.23 new "not possible in RevMan 5" incentives for authors0300%
3Go slower to go faster



3.1JPA relationships in ReviewDB08080100%
3.2Reduce number of manual regression test scenarios1354112427%
3.3Recruit 2 new team members0200%

Report September 6th 

NumberObjective / Key resultWorst (0%)Best (100%)CurrentProgress
1Remove blockers for MEs to advocate for RevMan Web



1.1MEs integrated in the sprint cycle0156/967%
1.2ME Exec satisfied with stories implemented0100%
1.3Blockers stated by MEs have been removed9.11111179.1111110%
2Demonstrate the added value of RevMan Web for authors



2.1Ensure a succesful references-only integration with Covidence05125%
2.23 new "not possible in RevMan 5" incentives for authors0300%
3Go slower to go faster



3.1JPA relationships in ReviewDB08080100%
3.2Reduce number of manual regression test scenarios1354112427%
3.3Recruit 2 new team members0200%

Report 23 August

NumberObjective / Key resultWorst (0%)Best (100%)CurrentProgress
1Remove blockers for MEs to advocate for RevMan Web



1.1MEs integrated in the sprint cycle0154/667%
1.2ME Exec satisfied with stories implemented0100%
1.3Blockers stated by MEs have been removed9.11111179.1111110%
2Demonstrate the added value of RevMan Web for authors



2.1Ensure a succesful references-only integration with Covidence0500%
2.23 new "not possible in RevMan 5" incentives for authors0300%
3Go slower to go faster



3.1JPA relationships in ReviewDB08000%
3.2Reduce number of manual regression test scenarios1354112427%
3.3Recruit 2 new team members0200%

Report 9 August

NumberObjective / Key resultWorst (0%)Best (100%)CurrentProgress
1Remove blockers for MEs to advocate for RevMan Web



1.1MEs integrated in the sprint cycle0152/367%
1.2ME Exec satisfied with stories implemented0100%
1.3Blockers stated by MEs have been removed9.11111179.1111110%
2Demonstrate the added value of RevMan Web for authors



2.1Ensure a succesful references-only integration with Covidence0500%
2.23 new "not possible in RevMan 5" incentives for authors0300%
3Go slower to go faster



3.1JPA relationships in ReviewDB08000%
3.2Reduce number of manual regression test scenarios1354112427%
3.3Recruit 2 new team members0200%

Link to the retro can be found here: Retro on ORKs: Quarter 3 (July - October)

Overall aim: Drive adoption of RevMan Web

  • Objective 1: Remove blockers for MEs to advocate for RevMan Web
    • Process: MEs integrated in the sprint cycle (participate in prioritisation, grooming and demo) - yes/no for each activity per sprint. yes/total = score   (RH)
    • The ME Exec is satisfied with features implemented yes/number of stories (verify with ME Exec) (RH)
    • A certain weighted % of blockers stated by individual MEs has been removed - Baseline is  82/9 (total number of blockers/persons who tried RevMan Web), current = 0, 7 blockers/person=100%  (RH)
  • Objective 2: Demonstrate the added value of RevMan Web for authors
    • Ensure a succesful references-only integration with Covidence (GvV)
      • Scope and user journeys agreed by both teams
      • Scope and user journeys validated with users
      • Collaboration process and definition of done agreed by both teams
      • Breakdown into releasable chunks agreed by both teams
      • Environments set up that cover the user journeys
    • 3 new "not possible in RevMan 5" incentives for authors integrated in promotional activities (e.g. study-centric data pilot success story, covidence integration ready, new commenting system, ...) (GvV)
  • Objective 3: Go slower to go faster
    • Implement JPA relationships on domain entities in ReviewDB (0% of relationships covered) - goal 100% (JHH)
    • Reduce number of manual regression test scenarios (baseline: ?) - reduce by 70% of baseline (IWH)
    • Run a succesful team-led recruitment for 2 new team members (IWH)
Start dateNotes
1 JulHoliday - no sprint
15 JulHoliday - no sprint
29 JulSprint 1: GRADEpro integration
12 AugSprint 2: GRADEpro integration
26 AugSprint 3 Search date
9 SepSprint 4 Validation report, assessed as up-to-date
23 SepSprint 5 Validation report, Setting Q4 objectives

Report September 20th

NumberObjective / Key resultWorst (0%)Best (100%)CurrentProgress
1Remove blockers for MEs to advocate for RevMan Web



1.1MEs integrated in the sprint cycle0159/1275%
1.2ME Exec satisfied with stories implemented0100%
1.3Blockers stated by MEs have been removed9.11111179.1111110%
2Demonstrate the added value of RevMan Web for authors



2.1Ensure a succesful references-only integration with Covidence05125%
2.23 new "not possible in RevMan 5" incentives for authors0300%
3Go slower to go faster



3.1JPA relationships in ReviewDB08080100%
3.2Reduce number of manual regression test scenarios1354112427%
3.3Recruit 2 new team members0200%

Report September 6th 

NumberObjective / Key resultWorst (0%)Best (100%)CurrentProgress
1Remove blockers for MEs to advocate for RevMan Web



1.1MEs integrated in the sprint cycle0156/967%
1.2ME Exec satisfied with stories implemented0100%
1.3Blockers stated by MEs have been removed9.11111179.1111110%
2Demonstrate the added value of RevMan Web for authors



2.1Ensure a succesful references-only integration with Covidence05125%
2.23 new "not possible in RevMan 5" incentives for authors0300%
3Go slower to go faster



3.1JPA relationships in ReviewDB08080100%
3.2Reduce number of manual regression test scenarios1354112427%
3.3Recruit 2 new team members0200%

Report 23 August

NumberObjective / Key resultWorst (0%)Best (100%)CurrentProgress
1Remove blockers for MEs to advocate for RevMan Web



1.1MEs integrated in the sprint cycle0154/667%
1.2ME Exec satisfied with stories implemented0100%
1.3Blockers stated by MEs have been removed9.11111179.1111110%
2Demonstrate the added value of RevMan Web for authors



2.1Ensure a succesful references-only integration with Covidence0500%
2.23 new "not possible in RevMan 5" incentives for authors0300%
3Go slower to go faster



3.1JPA relationships in ReviewDB08000%
3.2Reduce number of manual regression test scenarios1354112427%
3.3Recruit 2 new team members0200%

Report 9 August

NumberObjective / Key resultWorst (0%)Best (100%)CurrentProgress
1Remove blockers for MEs to advocate for RevMan Web



1.1MEs integrated in the sprint cycle0152/367%
1.2ME Exec satisfied with stories implemented0100%
1.3Blockers stated by MEs have been removed9.11111179.1111110%
2Demonstrate the added value of RevMan Web for authors



2.1Ensure a succesful references-only integration with Covidence0500%
2.23 new "not possible in RevMan 5" incentives for authors0300%
3Go slower to go faster



3.1JPA relationships in ReviewDB08000%
3.2Reduce number of manual regression test scenarios1354112427%
3.3Recruit 2 new team members0200%

Link to the retro can be found here: Retro on ORKs: Quarter 3 (July - October)