2023-08-02 - Product Committee

5 min

• Steve and Wes to define method to track relevant standards for each building block .

  • Esther to create epic for this.

@Sarah Farooqi

15 min

Use Case Draft

Feedback

• Ayush gave feedback that this use case is very similar to the unconditional social cash transfer use case

  • Sarah: the distinction is this use case focuses on cash transfers to vulnerable populations in climate emergency situations. Real time disbursement of funds only happens when for instance a climate emergency is triggered

  • Also there is different information that needs to be collected, and also different types of communications and coordination that needs to happen

• This use case doesn't necessarily have to be done by a government, it could also be done by an NGO or a multilateral

• Wes - there might be a few missing building blocks, for example, the real time eligibility determination. It would be helpful to get feedback from the technical teams on this

• Sarah - should the sectorial area of this use case be categorized as environment or climate

  • Use case team to have a followup discussion on this

• Sarah has shared the updated use case with external experts working in this space.

@Shukla, Ayush

10 min

Survey: https://www.govstack.global/2023usecases/

Is this needed?

• Esther - Yes, even if it is at a high level

• Sarah - The Exchange has both technical release notes as well as comms related to a release. Would be helpful to bring this up to the comms team so that we can plan for ongoing updates

What kind of release notes should we have?

• Esther - Centralized notes would be better, calling out specific BBs

• Steve - Put it into Confluence and link from the spec. Create a version history page (maybe?) and link to the notes from there. Level of detail could be Epics

• Saina - Include external feedback

• Nico - A very fine level of detail would be too much. Asked if there is functionality to see/track changes made in previous versions and see the differences (Wes to ask Rachel about this)

• Wes - have the search functionality that can take you to the Jira link with info on the changes that have been made (example to look into - release notes on OpenLMIS)

• Steve - Specification Landing Page

• Valeria - just have the links to see the historical activities of changes made

Agreed actions to be done:

• Create a release note section, and create a page for each release

  • High level activities related to each individual BBs

  • Have links to searches with detailed information on changes that have been made to each section

• Nico - scope of roadmap should be linked with and coordinated with other product related activities within GovStack. Creating a combined roadmap for all the GovStack activities

  • I.e., scheduling an event after a certain release

  • Ask BB leads to do trainings on their current and most up-to-date version of the specifications.

• Ramkumar - need to have more clarity on GC and PC roadmaps. Lets not mix up definition of product, services/operational issues within GovStack.

  • Nico - GovStack Products. PC is the best place for each team lead to join and participate to share updates

• Steve - need a broader definition of products - everyone should attend the PC meeting to share out about their work updates and events

• Wes - idea is to focus beyond the use cases and product activities. GIZ support in highlighting that all teams working on products should be part of the PC meeting for coordination purposes

  • Nico to come up with a proposal for this and also lead its discussion in the GC meeting.

  • Steve - important to have clear defined roles

• Sarah - need to have more streamlined approach - the PC to be in charge of a consolidated roadmap

@Wes Brown

5 min

Tracking Use Cases: Use Case Discussions

Comments

GIZ, Estonia, Dial, ITU