2018-10-11 VAN Dashboard Alignment Meeting notes

Date

Oct 11, 2018

Attendees

• Aida Coelho

• @Timoteo Chaluco (Unlicensed)

• @Ben Leibert

• @Christine Lenihan

• @Vidya Sampath

• @Swetha Srinath (Unlicensed)

Goals

• 1^st 30 minutes: SELV+ dashboard

  - Training schedule with Ona and VillageReach team (Christine to present idea for this)

  - Troubleshooting guide and how-to guide (Vidya to present idea for this)

  - Strategy for SELV+ dashboard for next 3 months – stakeholder introduction, and actual usage (Timoteo to talk about what he would like to do, what are current problems stopping him doing this, support he needs)

• 2^nd 30 minutes: overall VAN processes and strategy roll out to provinces and districts

  - Christine and Ben drop-off (but welcome to stay if they’re interested in listening in)

  - Rest review VAN workplan key points and comments made by Timoteo and Vidya and finalize

Discussion items

1^st 30 minutes: SELV+ dashboard

• Training schedule with Ona and VillageReach team (Christine to present idea for this)

  • Point person: Ben taking this on and moving into a PM role

  • Establishing communication with Ona: Ensure we have ongoing support, some communication with Ona support – e.g. periodic check ins

  • Support from Ona: We have contract with Ona to support the dashboard in the next year, some ability to troubleshoot, and make limited changes. But note that Superset is easy enough for non-developers to use and make changes in

• Training schedule: Putting in place communication and feedback loop processes that we don’t have, to ensure more people on the VR team prepped for troubleshooting

• Ben’s preference: Timoteo should interact with Ona directly to trouble shoot. Just put a public record of the interaction / of what went wrong e.g. JIRA Confluence tickets; Service desk

• Action Item: @Ben Leibert to put in place the training schedule and processes

• Troubleshooting guide and how-to guide (Vidya to present idea for this)

  • “How to” guide for SuperSet: In English and Portuguese – doesn’t exist, but there are meeting notes on JINA Confluence. But they are mostly on troubleshooting guides

  • 2 types of guides: a) How to guide b) Troubleshooting guide

  • Training Option 1: Felimone, Timoteo on Moz side; Swetha and Victoria on Seattle side to get official training, and will be responsible for documentation

  • Training Option 2: Sifting through JIRA’s tickets and gathering info

  • Action item: When training schedule is set up, documenters will be identified to pursue Training Option 1: Felimone, Timoteo on Moz side; Swetha and Victoria on Seattle side to get official training, and will be responsible for documentation

    • https://superset.incubator.apache.org/tutorial.html - starting point for documentation

• Strategy for SELV+ dashboard for next 3 months – stakeholder introduction, and actual usage (Timoteo to talk about what he would like to do, what are current problems stopping him doing this, support he needs)

  • Presenting to stakeholders: Dercio presented this at a Data Quality Planning Workshop – but he didn’t go into detail since the data viz was still being ironed out

  • Getting Dashboard “client ready”: Visualization needs to be refined, lot of missing information, this needs to be addressed since provincial and district level trainings need to happen eventually. Not conducive to analysis at the moment.

  • Uploading data from different sources: Periodocity of sending data? The cycle of data being sent for data to be uploaded on Dashboard needs to be addressed

  • Questions/Comments

    • Questions from Aida: Presented to GAVI in January; DQP Workshop. Are EPI people using it? Didn’t see this mentioned in WHO DQIP (?), need to see the dashboard make more progress.

    • Timoteo: Things mentioned above need to be improved before it is ready to be shared. This fixing may be need developer help.

    • Question from Ben: Do you have a clear idea of what needs to happen for dashboard to be ready for presentation?

    • Timoteo: We tried to present to stakeholder, but it would have garnered very negative feedback. More internal discussion needed to arrive at the point (e.g. Vidya)

    • Felimone: Was in Niassa, PAV said it is a useful tool but they wanted to see more of the tools they are using reflected – they use Excel files etc in their normal activities. But it would be helpful to get a sense of which of their on-going analysis / activities could be incorporated into the dashboard

    • Timoteo: What Felimone is suggesting may be a second-phase iteration

    • Vidya:

      • · Strategy for sharing with external stakeholders: To Aida’s point: we need a strategy to get external stakeholders (including WHO DQIP), i.e. by month x, we will release it, get stakeholders using the dashboard, getting their feedback etc.

      • Type of stakeholders to engage / to promote to: To keep the things focused, we will focus on Central level stakeholders.

      • · What needs to happen to Dashboard: As a team, we need to finesse the storyboarding of the Dashboard – right now the placement, visualization aren’t strategic. Everything is cluttered. Tweaks to how the dashboard is set up visually, using data / graphs that are ALREADY in place.

  • Action Item: Swetha will work with Ben and Timoteo to brainstorm on Visualizations / storyboarding

    • Ben will send credentials to Swetha

    • Swetha and Timoteo will play around and come to the meeting on Tuesday 16^th October with ideas. Ideally, it would help to have Ona join in on the meeting to help in scoping the changes being suggested à Clay to attend as well.

    • Note from Christine: What is the minimum that needs to be done to roll out the dashboard à Prioritize pre-roll out tweaks vs tweaks / iterations that can be done post roll-out. Ensure that major technical tweaks needed from Ona.

  • Action item : Stakeholder engagement / launch strategy – document that lays the purpose and usage plan of this dashboard → we will introduce activities specific to this during VAN Workplan meeting with Aida.

  • Action item: Since users haven’t been consistently emailing data for upload onto the dashboard, there are data gaps for past periods. Would it be possible to have old data to be retroactively submitted to the system to fill some of the data gaps we are seeing on the Dashboard?

    • Ben to confirm this with dev team, but it is unlikely to be a problem

Action items

Decisions