2022-09-28 - Product Committee

Introducing the Product Committee

@Wes Brown

Setting the meeting agenda: 

• Goal of these meetings is to be inclusive, not exclusive. Recommendation on other individuals to invite to these meetings are welcomed and encouraged. 

• This Confluence link is where meeting notes, topic backlogs and updates can be found.  

• Meeting agenda items will be tracked on here. Committee members can add topics/agenda items they wish discussed in upcoming meetings. 

• Intent is that during or prior each meeting, to go through the backlog and figure out what are the high priority topics to discuss. 

• Role of the PC

• Are we missing anyone?

• Links:

  • Confluence: Productarchived

  • Slack

Product Committee Scope of Work

@Yolanda Martínez (Unlicensed) / @Eskandar, Hani

General feedback on the Product Committee Meetings scope/priorities: 

• The Product Committee should have clearly defined outcomes and deliverables to ensure there isn’t massive scope creep with the country engagement and technical committees. 

• Important to ensure that all Committee members have the same understanding of what the scope of work of the Product Committee is and how it collaborates/coordinates with the Technical Committee. 

• As we kickstart the Product Committee meetings, it might be best to focus on one topic to ensure seamless flow, at least until these meetings are more established.  

• Discussion could focus on insights and relevant topics emerging from Country Engagement and Technical Committee meetings. 

• The role of the Product Committee could be to make sure Govstack’s product and BB specifications are good enough. 

• Committee members could work on developing comprehensive user journeys with relevant examples on the type of services being implemented using the BB approach. 

• This can be done through close collaboration with the selected system integrator in charge of producing 10 exemplar/example/reference use cases of digital services. I.e., EPRI? Use case in Rwanda, the G2P use case for government payment etc,.  

• Great example to look into - EGO Foundation, they have developed 30 open-source components building blocks. 

• DGIT: https://docs.digit.org/    

• GovStack’s success will depend on being able to identify and demonstrate the right use cases. Product Committee should focus on the entire user journey – from end-to-end journey when seeking government services. 

• The Product Committee needs to interact with the GovStack country engagement teams to understand the use cases prioritized by governments they are working.  

• Our team should see if we have the capabilities and functionalities within our building blocks or sandbox product to deliver on those use cases. 

• Include more GovStack country team members in the Product Committee – important to have people who are really working on use cases and user journeys involved. 

• One outcome that we can take from today's session is to decide what would be the first use case digital service or user journey that we would like to prioritize as the Product Committee – i.e., start with mother and child, then the World Bank’s G2P digital service, the Ukraine example, and then the community of practice of health. 

• Product Committee should decide on the structure of user journey templates, documentation, and terminologies.  

  • Need to define our terminology

    • What is a Use Case? User Journey?

     

Roadmap Review

@Wes Brown

Roadmap

Deployment Updates

Use Case Review

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. 

• To 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. 

• During the next meeting: 

• Go through all definitions in the technical specifications and relevant GovStack documents that had been created, and review/agree on common definitions. 

• Walk through the entire playbook on digital service design. 

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

• Release Process

  • GovStack Releases vs BB Releases

• Review GitBook Playbook and Terminology