2022-10-05 - Product Committee

Review Action Items

@Wes Brown

Roadmap Review

@Wes Brown

Roadmap

• Basing work on spreadsheet, we have a view of a roadmap.

• @Taylor Downs Who decides what work a Building Block needs to do? @Wes Brown PC to define the high level “functional spec”

• @Rachel Lawson (Unlicensed) Would it be better if each of these roadmap items was an Epic (or equivalent) including definitions of done.

• Recent comms to BB Leads has been not to detail concrete things to do and more about time spent

• “How do we roll these individual BBs together into a single release?”

• When we get up to speed on using Jira etc, maybe we then get better estimates?

•  

Deployment Updates

None to discuss

Use Case Review

@Sarah Farooqi

Review of various types of use cases:

Open

Questions:

• Ramkumar - Need to define terminology across disciplines, GovStack-wide. Shared a example presentation:

Open

• Margus - Journey-based approach was created to streamline services, but this could result in multiple instances of BB

Next Steps

• Product Committee members to get back to Wes on any other individuals to have participate in these meetings. 

• Committee should identify few action steps to start with and move forward with them i.e., in the next 2-3 months agree on what the GovStack system integrator will do, and which services they need to invest in. 

• Identify and document reference use cases, the Product Committee should focus on engaging with diverse communities of practices and partners that are already working on real use cases and interoperability within their own setting.  

  • I.e., look into India’s digital platform 11 use cases, the health community of practice that is part of the DPGA alliance, cash transfer use cases by some of our development partners, and social protection interagency(?) - World Bank and ILO initiative.  

  • Product Committee/ Wes could engage these actors to understand and compare real life use cases of social protection services.  

• Agree on terminology and definitions – especially when it comes to how the definition of use cases and user journey is used by the country engagement team and the technical building blocks team. These definitions can be placed in a common repository in GitHub where all can refer to for clarification. 

Topic Backlog

This backlog is a list of potential topics that we can discuss:

• Use Cases

  • Current Use case review

  • Use case format

  • Process for evaluating country/community use cases

  • Use case tools (Product Catalog, Gitbook, others?)

  • Need to pick an initial use case/user journey to work through

    • Proposal for Mother & Child (digital service is well evaluated and documented)

    • World Bank G2P

    • DIGIT

• GovStack Processes

  • Interacting with the broader community

  • Interacting with the Tech Committee

    • Process for communication use case changes to the TC and BB leads

    • PC owns use cases and TC owns specifications?

  • Interacting with Working Groups

  • What is the GovStack product? What are we building (from @Taylor Downs )

• Release Process

  • GovStack Releases vs BB Releases

• Review GitBook Playbook and Terminology

• Walk through the entire playbook on digital service design.