2023-10-11 - Product Committee

5 min

@Sainabou Jallow

20 min

Use Case: https://app.gitbook.com/o/pxmRWOPoaU8fUAbbcrus/s/YLLEfCKTnmzAMDSDzJJH/~/changes/66/use-cases/agr-1-market-linkage-1

• focus on provision of advisory services for farmers

• Margus: Should we still include the SDGs although they will not be reached?

• Sainabou: We should keep them as there is still time to go and the targets are included as a filter on the exchange.

• Sarah: Not opposed to Margus idea. This level of detail might not be necessary.

• Farina: Agrees that mentioning the SDGs only is sufficient.

• Meelis: Agrees as well.

• Saina: Proposes that the use case template should be reviewed next week.

• Wes: To include the SDGs is valuable.

• Margus: SDGs are relevant but the targets are not.

• Saina: Should the adjustments be made for this publication or later on?

• Wes: I would leave it as is for this publication. But it can be incorporated in the next publication.

• Margus: It can be done for this publication, the change is done easily.

• Wes: It could be political if we don’t include the “by 2030” part into our description because it is part of the official text.

• Margus: Clarifies that we would just highlight the SDG level and not mention the target level.

• Sarah: Agrees with Margus. We would have to update the targets in the future because they are subject to change.

• Margus: DPGA is also only referring to the SDG level.

• Decision: We will update the existing use cases and from now on will reference the SDGs and not the targets anymore.

@Wes Brown

20 min

Q: Are there any priorities for the time after this publication?

• Margus: Proposes a revision of the specifications, as some of the specs are use cases. i.e. identity BB. It includes more information that just specs. Goal could be turn some BB into smaller BBs.

• Wes: Agrees that a review is a good idea. Some BBs need to be decomposed.

• Meelis: Would like to see a review of the infrastructure. Create a check-list for onboarding purposes. Include further considerations about capabilities / service blocks.

• Margus: Analyze: How can specs be used for procurement?How can governments take the specs and use them for ToRs?

• Meelis: We can also discuss the vision that GovStack has with regards to the procurement and application of GS approach.

• Margus: If we put ourselves in the shoes of a government official or talk to government official, we’ll be able to provide services that fit their needs.

• Psramkumar: Sometimes it is not clear what exactly GovStack can provide, so we need better expectation management. Also, we can provide examples and pathways that illustrate application options.

• Margus: technical requirements are not part of what GovStack can provide. But the functional layer can be provided by us.

• Psramkumar: Guidelines and instructions to set up your own version of the sandbox should be provided.

• Farina: The Sandbox DiY documentation can be a starting point: Do It Yourself - sandbox (gitbook.io)

Ideas:

• Service blocks, interaction between BBs and other architecture levels

• Spec review incl. external feedback

• Application of specs for procurement purposes, describe procurement support options

• Review structure and target of specs, set expectations correctly

• Service blocks and connecting them to the specs

@Wes Brown

5 min

• Review the use case template

• Discuss the eMarketplace building block and how to include it in the Market Linkage use case

• Discuss working on a procurement platform reference use case

GIZ (for ITU), Estonia, Dial, ITU