Reporting questions and user personas
Description
Confluence content
QAlity Plus - Test Management
Checklists
Activity
Brandon Bowersox-Johnson April 4, 2017 at 7:27 PM(edited)
Thanks, . Your input makes a lot of sense. I updated the Reporting wiki and dashboards wiki based on your input.
Dércio Duvane April 4, 2017 at 8:55 AM
Hello , and ,
Really sorry for this way tardy reply, things have really been busy.
Bellow are a few notes from some conversations I had with and Gregorio,
1. Whom wants the Reports
This reports are/should be designed to managers and deciosion makers, i.e., logisticians, program managers (districtal, provincial and national levels), directorates (public health, any other interested program) and key stakeholders, partners and donors like UNICEF, GAVI, etc.
2. How they want to access them
We had mixed feelings regarding to this question, it's desirable to have this on the same system that collects the data, like a dashboard, on which they can make a few or use predefined filters like province, program, antigen, etc. It's also important to have this reports sent out periodically to other stakeholders that might not be able to use this dashboard on an *email *in pdf or any other specific format, like the current tableau files for SELV.
3. When to receive this reports
Depending on the source/type you choose for a report, different periods are acceptable, i.e,
on the dashboard, it would be immediate - it's important to notice that a warning should be posted on this as the data might not be fully uploaded on to the system
By e-mail, a monthly report would be more interesting.
4. Types of reports identified - _Resources to be displayed/available on the reports _
Tabular data;
Graphs;
Charts;
Maps;
5. Skills
Tableau
Jasper
SQL
Java
Brandon Bowersox-Johnson April 3, 2017 at 10:37 PM
We would still welcome any feedback from you on this. We had a good Product Committee conversation.
Josh Zamor March 21, 2017 at 5:47 PM
et al: I left a comment on the page. Thanks for starting to get this together. Overall I think we need to keep drilling down into whom can do what, whom can typically be hired, perhaps even a typical budget for report writing contract work, etc
Could we source any of this budget/customization work from existing implementations? Even having guardrails would be useful: what's too expensive, what sort of lead time worked / didn't...
Mary Jo Kochendorfer March 21, 2017 at 5:11 PM
Asked and and PC to review the https://openlmis.atlassian.net/wiki/display/OP/Reporting+and+Analytics I pulled it together.
Details
Details
Assignee
Mary Jo KochendorferReporter
Josh ZamorStory Points
Components
Sprint
Fix versions
Priority
Blocker
Time Assistant
Open Time Assistant
Time Assistant
The goal of this reporting task is to define what we mean when we say "implementers want to build OpenLMIS reports" or "OpenLMIS needs a reporting solution".
To do that lets answer the following and adding these to our personas:
answer whom wants the reports that are made and how they want to access them (e.g. emailed, in the application or even as part of a workflow, in a separate BI&A tool, offline), and when they want to access them (immediately, can be a few minutes old, many hours/days old)
define terms for the types of reports identified (e.g. offline reports, donor visualizations, tabulated/paginated printable reports, dashboards)
for the types of reports implementer's want to build, identify what technical skill set is required (e.g. knows SQL & Excel jedi, Java and a UI developer, Jasper/Pentaho/BIRT, Tableau, DHIS2)