...
| Page Properties | |||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||
|
Status
# | Step | Status |
|---|---|---|
| 1 | Responsible prepares rough business analysis/reqs doc | |
| 2 | Get CHAI review | |
| 3 | Get Akros Review | |
| 4 | Get Ona feedback | |
| 5 | Responsible - 1 iteration for feedback | |
| 6 | Ona sign off | |
| 7 | Ona tech spec scoping | |
| 8 | Ona LOE | |
| 9 | Ona scheduling |
...
- This document covers 7 user stories in the C5 module
Jira Legacy server System JIRA jqlQuery filter=10032 serverId 3420e60a-4e6f-3f80-8335-059c22bb40aa - The initial thinking was that these stories would focus on user performance management as a differentiator to DHIS2
- Metrics will therefore need to be collected at a user level
- MVP is to add Google Analytics (GA) tags to each WebUI page and track page views
- Next iteration would be to develop the GA reports
- Analytics on the Android device will not be picked up by GA
- 222 and 223 - Reporting Lag and Reporting Time reports will require some code change and enhanced ETL so that relevant fields are collected in the Android APp and Server and stored in the data warehouse for each event
- Can use User_ID to track users - https://support.google.com/analytics/answer/3123662?hl=en.
Definitions
Requirements
Mock-Ups
...