Skip to content

3) DIV Co Leads Meeting Notes

Randy Yee edited this page Nov 5, 2020 · 13 revisions

DIV Co-Leads Meeting: 11/1/2020

Attendees: Jamie, Yaa, Randy

  • GCB Project Board Setup
  • Botswana Request (reach out to Kiefer for maps)
  • Workplan
  • Landscape Analysis pending
  • PSC topics for tomorrow (calendar, Landscape feedback, unit testing)
  • SharePoint features discussed

DIV Co-Leads Meeting: 10/1/2020

Attendees: Jamie, Yaa, Randy

  • Pano Tech Committee: Need to ask for support from Janice for TX Dossiers
  • DIV Meeting Agenda:
    • GCB Subgroups
    • Landscape Analysis Team to meet with PCDs to discuss results
    • Botswana Request
  • Botswana Request: Yaa to do the data pull, Shazad and Randy to mockup some visuals
  • Spotlight Subgroup pending Q1 discussions
  • DataViz Library data governance issues and potential solutions

DIV Co-Leads Meeting: 9/24/2020

Attendees: Yaa, Randy

  • Pano Tech Committee: Cancelled this week
  • Janice to give new feature orientation next week
  • Sent proposed FineAge 2018 - 2019 email, waiting to hear back
  • DIV workplan feedback especially member LOE's
  • Botswana recap need to schedule a call early next week
  • Agenda for next general meeting
  • Need to discuss Spotlight group

DIV Co-Leads Meeting: 9/17/2020

Attendees: Yaa, Randy

  • Pano Tech Committee:
    • Need to talk more about age disagg level selector vs what we are planning to replace with attribute level selector
    • Training to be done 9/28 need to reconfirm
    • Ask for unit testing checklist
  • Botswana Infographic Request:
    • Need to touch base with HSS for collab
    • Expecting Bots to send us DREAMS data
    • FSD has budget data but may not be comprehensive
    • Need to clarify roles and responsibilities between DIV and HSS
    • A lot of data already on pepfar.gov, but need more clarification of data sources
    • Still need to figure out appropriate platform/software for infographic, ideally something that can be handed off to them
    • Next Steps: Setup meeting with Jamie, HSS, Travis (if possible); potential follow-up call with Sean to figure out requirements of deliverable etc.
  • Draft Workplan
    • Figure some of the GCB milestones (Randy)
    • Yaa to figure out next year Spotlight and Pano activities
    • LOE tab needs to be updated by members
    • Update work products tab
  • ICPI Learning Collaborative Sprint Team - how do DIV activities fit in?
  • Need to touch base with OCM & Jess Handy for the transition courses in PVA (Slack and Github up; Github session needs to use ICPI PPT template)
  • Landscape Analysis:
    • Next step for the team is summarizing the findings
    • Should hold post-mortem with PCDs to share findings
    • Figure out how to formalize landscape analysis
    • Brownbag after Lead submission and review? Focused more on process and less on results
  • Asia Region follow-up with Jamie

DIV Co-Leads Meeting: 9/2/2020

Attendees: Jamie, Yaa, Randy

  • Botswana Infographic Request Clarification
  • Scheduling of Microstrategy 2020 Demo for ICPI
  • Post-Retreat Action Plans:
    • Spotlight Support
    • Field Panorama Content Developer
  • Sharing BI tools interagency discussion
  • GCB Subgroup recap
  • Next steps for QC Tools Subgroup
  • Meeting to revise workplan next week

DIV Co-Leads Meeting: 8/27/2020

Attendees: Yaa, Randy

  • Pano Tech: To discuss agenda items from cancelled meeting last week
    • Q4 dossiers planning to implement new features - selector & hyperlinks, training plan needed
    • Planning to consolidate single OU and single OU site
  • Will submit to PSC the consolidated Q4 updates
  • Agenda for next meeting
    • GCB subgroup initial meetings/planned activities outbrief
    • Asia Region BI Presentation outbrief
    • Landscape Analysis updates
    • QC Tools need to be submitted
    • Viz of the week
  • Workplan review/updates (due Sept 25th)
  • Retreat action plan:
    • Spotlight Review and Recommendations
    • Expand content developer to include more field team

DIV Co-Leads Meeting: 8/21/2018

Attendees: Brittney S., Aaron C., Jess B., Katya N., Katie O.

  • DIV BI transition: Katie O. taking over as co-lead. Pooja will serve as Pano liason.

    • Pooja will attend all DIV meetings
  • Workplan & upcoming priorities

    • MER Refresh - what input we need to give around MER transition. More falls into role of DAQ
      • Pooja & DAQ
    • DIV role in POART prep?
    • Analytic workspaces: check in w/Jasmine on what DIV-BI role should be and what Jasmine's role is? - Jess & Katie O.
      • pilot can't move forward until we can figure out how to share dashboards btw agencies & countries
      • Pooja can also cover, but limited. Pilar & Alice are main contacts.
    • GCB
    • Cross-training on existing tools - ICEE role
    • What is ICPI's country strategy? only have Reverse TDYs (ref 1c). - bring up at next ICPI All Staff/Senior Staff meeting - what has been the progress? - (Katya will send this as agenda item). How are we engaging with the field - a webinar is not enough. Maybe data analysis & use workshop.
    • Trainings
      • Tableau, GitHub, putting on 2nd R Training
      • how do we make them more field friendly? we need to train up ourselves to be able to confidently roll it out to the field. not everyone is at the same place with R for example. Tableau - lot of countries are yearning to use it but there are licensing issues w/potential problem. Unsure how useful GitHub.
      • Transition training materials to Edx for field friendly.
  • Time/duration - yes, every other Tuesday @ 1pm still works

  • Upcoming leave/TDY

    • Katya out 8/24, 8/30 - 9/6 on AL; 9/7-14 TDY (see ICPI calendar for details)
  • AOB

  • Next steps:

    • Katya & Aaron to meet to review GCB portions of workplan on 8/28.

DIV Co-Leads Meeting: 4/17/2018

Attendees: Brittney S., Aaron C., Jess B., Katya N., Katie O. Jasmine B.

GCB sprints:

  • GitHub Training
  • Style Guide
  • How to organize back end of tool
    • "Show & Tell" series on what people are doing with their tools
      • Automation of tools
      • Don't want to prescribe how backend should be setup
    • Using R - documenting best practices
      • Once you run your code, upload to GitHub
    • How do we structure tools so that they all look the same in the backend
      • Title
      • Tab labels
      • Approach for backend setup
    • Sprint - DIV leads
      • Bring in only "tool-builders"
      • Write up loose guidance for what tools should look like
      • Audience: ppl have built tools, Excel users, who have a potential to update tools
        • Include people who previously created products, but may not do so now
      • Next steps:
        • OCM to provide list of tools & tool builders
        • DIV track this in a sprint/issue

Analytic workspaces

  • Planning regular workshops with Pilar & Alice

Items not addressed - potentially schedule a Thursday meeting to follow-up

  • Other sprint priorities

DIV Co-Leads Meeting: 4/03/2018

Attendees: Brittney S., Aaron C., Jess B., Katya N.

  1. Clusters Presentation debrief
  • Sub-group updates
  • Other Cluster + DAQ collaboration
  • Awaiting feedback/structure from Leads
  1. Work plan Review - will wait for feedback/structure from Leads
  • Staffing gaps
  • Timing of deliverables
  1. Analytic workspaces - Brittney will announce update at Inbrief
  2. AOB

DIV Co-Leads Meeting: 3/30/2018

Attendees: Brittney S., Aaron C., Jess B. Katie O., Katya N.

  • Clusters presentation 3/30: Template for presentation coming out soon
  • Review & Discuss:
  • Brainstorm reorganization of DIV inbrief slide?

Summary: the co-leads reviewed the SOW and made changes located in DIV GitHub Documents and posted to pepfar.net

Next steps:

  • Review and Update SOW prior to clusters meeting (on 3/30), by 3/27
  • Draft presentation using template to share with larger DIV on 3/27 and Coordination Cluster meeting
  • Update workplan (issue #14) by 3/27
  • Discuss ownership/collaboration point regarding scope of Knowledge Management/Visualization Library with OCM. Some of the previously defined objectives now seem to fall under ICEE and OCM.
  • Map workplans with DAQ (Jess created issue #44) to coordinate

Notes 12/12

Viz Library:

  • Doodle poll has been sent to group to assess scheduling meeting before the holidays. Initial results indicate that team may not be able to identify a time that works for all
  • Risk noted: Group may need assistance with initial start-up tasks, including identifying a platform for tracking library, identifying needed metadata for tools
  • Katya offered that the team could look at DC Open Data, a site that tracks metadata about all datasets. Could be helpful for brainstorming.
  • During next week's Inbrief, Katie is going to ask for input from the broader ICPI group if anyone can assist with brainstorming metadata to collect about our tools.\

GCB:

  • There has been good discussion about the color scheme. More feedback will be needed from other subgroups of DIV.
  • There are partner/mechanism names that we would like to post on this GitHub page. Initially heard that we could not post these names. Team confirming whether the names are also posted on Zendesk or other public sites.
  • Kristy compiling a list from DIV and other ICPI stakeholders of SharePoint issues, to be shared with OCM once complete.
  • Noted that a few items need feedback from larger DIV group, and we do not have a list serv. Jess to update ticket noting all DIV membership with email addresses and subgroup affiliation so that whole group can be contacted by any member as needed.
  • Discussion around creating shorter-term working groups (similar to ECT Short Term Task Teams) for specific DIV projects and initiatives. Katya to bring this concept up during OCM meeting on Thursday, and bring up in Inbrief Monday. Jess to create placeholder ticket.

BI:

  • Upcoming integrated prioritization for Pano Q1 this afternoon
  • Collaboration needed with GCB and DAQ to discuss downstream impacts on tool owners of data element name changes coming in Q1. Jess to update ticket, Katya to add list of names from GCB, Jess to send email coordinating a time to meet with DAQ.