Start logging useful data in RevMan Web

Owner: Rebecka Hall
Roadmap history:
Selected for Next in Q2 update
Reason for archiving: Too small to be a roadmap item and better to progress within measuring value of each roadmap item, will remain as tickets on the backlog

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

There is currently no good way of survelling how users work in RevMan Web. We are only following log-in events. 

Logging can be used to:

  • more appropriately follow the uptake of RevMan Web
  • gather data to resolve support tickets
  • identify working patterns in RevMan Web to understand how and which new features to implement
  • to verify the value of implemented features 

How can the value delivered be measured?

We have a clear and useful way of assessing RevMan Web uptake.  
Number of support tickets using the logged data. 
Number of stories where the value can be evaluated using the logged data.
Number of stories identified by analyzing logged data. 

Which assumptions are made in relation to the value?

What are the dependencies for fulfilling the business value?

Identifying which data to log in order to fulfill the value.

What are the risks related to this roadmap item?

That we invest time in logging the wrong data. 

What is included in the scope of this solution?

RMW-689 - Getting issue details... STATUS

RMW-1130 - Getting issue details... STATUS

RMW-1188 - Getting issue details... STATUS

How much time do we estimate to implement this roadmap item?

This is a guesstimate made by the Review Production Team based on known information about the roadmap item and the capacity of the team at the time of estimation (June 2020).

Small = within 1 sprint = 2 weeks or less.