Non-Cochrane reviews phase II (individual use)

Owner: Rebecka Hall

Project team: 

Rebecka Hall (responsible for development in RevMan Web and overall user experience)

Ann Shackleton (responsible for Porto and CRM development)

Gert  (responsible for overall technical architecture)

Paolo & Martin (responsible for building a landing page for RevMan Web and a shopping basket)

Roger Tritton (responsible for business case and overall project management)

Richard Hollis (responsible for sales experience for Organizations)

Ursula Gonthier to be followed by Eva Krainitzki (responsible for Knowledgebase article and support)

Project page: Meetings - RevMan Web for non-Cochrane reviews

What business value does this epic create? / Which problem is this epic trying to solve?

Link to strategy:  GOAL 1 Streamlining production of reviews and simplifying editorial systems and processes

Future of review production project: Retire RevMan 5

Continuing to offer RevMan to non Cochrane users is a requirement for retiring RevMan 5. So far, organizations are supported but this epic is to support individuals in purchasing a subscription and using RevMan Web. The key audience is academic users of RevMan and reductions to subscriptions will be available for TBA. 

The income from indivudal subscriptions will help fund continued development of RevMan Web. 

How can the value delivered be measured?

At least 3 individual subscribers by end of 2022. 

Income from individual subscriptions reported by quarter.  

Which assumptions are made in relation to the value?

Supplying an up-to-date and continuously improving web application to an acceptable price range is more valuable than maintaining a free desktop application that is unsupported. Note that the pricing for RevMan Web individual subscriptions can be changed in the future if needed. 

What are the dependencies for fulfilling the business value?

  • Development in Porto, see PORTO-146 - Getting issue details... STATUS (specific dependencies will be noted in stories)
  • RevMan landing page in place, not a dependency for releasing stories but dependency for launch. 
  • Shopping basket in place, not a dependency for releasing stories but dependency for launch.
  • Merging of Porto and RMW KBs, not a dependency for releasing stories but a dependency for launch. 
  • Formats for download review data agreed  

General requirements page (also includes other Porto phases): Development Items

Mockups for landing page, alignment of RevMan-Porto UI: Mockups landing page and My reviews 

What are the risks related to this epic?

It's likely to take time before the cost of development is returned through subscriptions. 

Cocrhane's brand is negatively impacted by selling software that was previously free.

What is included in the scope of this solution?

  • (MUST HAVE) RMW-3011 - Write access to individually owned reviews to require an individual subscription by the author BACKLOG  
  • (SHOULD HAVE) RMW-3016 - My reviews re-design BACKLOG
  • (SHOULD HAVE) RMW-3017 - Update top navigation to align with Porto BACKLOG  
  • (SHOULD HAVE) RMW-3020 - Move review specific information from top navigation bar to separate row BACKLOG  
  • (SHOULD HAVE) RMW-3029 - Download review data
  • (SHOULD HAVE) RMW-3024 - Delete versions that are outside version retention policy BACKLOG  
  • (COULD HAVE) RMW-3018 - Filter on review title BACKLOG
  • (COULD HAVE) Show code/review number, relates to RMW-2784 - Getting issue details... STATUS (suggest waiting until Cochrane starts using/is using Porto)
  • (COULD HAVE) Search by code/review number  (suggest waiting until Cochrane starts using/is using Porto)
  • (COULD HAVE) Filter by review owner or contact person (wait until Cochrane starts using/is using Porto or include?)
  • (COULD HAVE) Filter by project type (suggest waiting until Cochrane starts using/is using Porto)
  • (COULD HAVE) Filter by task status (suggest waiting until Cochrane starts using/is using Porto)
  • (COULD HAVE) RMW-3025 - Update API documentation for non-versioned endpoints BACKLOG  
  • (COULD HAVE) Changes to Practice review area (Block use of import, needs more description for brand new users, incl differences between features of practice reviews and non-cochrane reviews (Link to feature table?), could also do improvement RMW-2895 - Getting issue details... STATUS  

  • (COULD HAVE) RMW-3026 - Make sure arrays are wrapped in non-versioned API BACKLOG
  • (COULD HAVE) Survey popup for RMW user experience and sales process
  • (COULD HAVE) Show contact person's gravatar in addition to logo for individually owned porto reviews 
  • (COULD HAVE) Easy access to manage review options in Porto (Add author, transfer review, deactivate review)

How much time do we estimate to implement this epic?

MUST HAVE is done

SHOULD HAVEs: S (within a sprint) assuming formats for RMW-3029 - Download review data are in place and agreed. (2022-09-08)