2023-01-11 - Product Committee

Presenter

Time

Notes

@Wes Brown

5 min

• Wes to follow up with Rachel directly on the 1st action item.

• Jaume to work on translations in 1-2 months as he is waiting for additional documentations to be completed first. This will now be considered a low priority action item.

• Ramkumar - will share the document soon, but for now the only product we have in GovStack is specification. Reality is product is a generic term.

  • Yolanda: as we develop use cases and the work we are delivering, then the definitions will become more clear. We can review the entire process of supporting gov’ts, prototyping being done etc., then as an initiative decide if we need to make changes to the current structure and define terminologies.

@Jaume DUBOIS

15 min

• Powerpoint deck presented - link

• The use cases have similar formats - always includes onboarding someone - where they have to fill in a couple of forms, submit certificates, documents etc,

• Steve: agrees with the approach and is useful for framing the approach of the work being done.

  • what Jaume is describing as Capabilities are very similar to what the SDG Framework document calls Workflows.

  • Workflows = business process enabled by interactions between multiple BBs.

• Ramkumar: useful from the terminology perspective - having agreed definitions of feature, interaction etc. Technical building blocks can be reused. Communications could become a functional building block.

• Jaume: open to changing the name ‘integration’ and leverage other work that has been done. Once we have finalized new cases, we have to build the capabilities of actors that have to implement them.

  • If we focus too much on end functional use case, we will miss the management actions that's necessary to ensure it is useful and implementable.

  • Capabilities definition came about as a way to identify different ways to authenticate yourself.

• Sarah: agrees with the findings based on research work she had done in the past: the chart on page 9-10 lists some "steps" that she thinks can be reusable capabilities. Might be useful as teams work through this task. https://docs.google.com/document/d/1_DeONard3-PmrpFjx8XzpxlDuoMMm7NU6aIMft4eONE/edit#heading=h.kpk1djepvfke

• Wes:

  • likes the term capabilities.

  • Similar to the workflows already on the Catalog.

  • Might be great to get feedback from the technical team, and decide how to incorporate it as a concept.

  • Likes the idea of capabilities ways to focus our publications. it would be helpful decide the areas we want to focus on for publications and will help focus our efforts. Similar to having specific feature steps to prioritize.

  • First next step is to make sure the technical committee agrees with this and decide how to move forward.

  • First publication - end of March - it is too soon to incorporate these ideas in this publication. Not enough time to make changes to the use cases etc, by March.

• Yolanda: this can be tested and reiterated in the country engagement meetings taking place.

• Next steps:

  • List the capabilities - go back to the BB and figure out what are management use case they need around their building block.

  • Having priority management of what needs to be built out first.

@Wes Brown

5 min

The currently defined relationship:

Country Requirements → “Product” Use Cases → Technical Specifications → Application Development

@Wes Brown

10 min

Using the term “product” for this committee has been confusing for a long time. Let’s figure out a better (or at least less overloaded) term and use it instead

@Wes Brown

10 min

Use Case Document: GitBook

Feedback

• Steve: shared link of the Implementation Template

  • Example of postpartum implementation example

  • Technical committee to discuss the product use case template Wes has developed and how to integrate it into the Technical team’s implementation template.

• Wes: individual implementation - that's going to be transitioned to a high level text use case to something that is more technical and incorporates one or more building blocks.

  • The goal of this document is to be a high level product use case with steps in it that leads to example implementations.

• Ramkumar: how do we blend ready made capacities to use case explanations.

• Jaume: what are the capabilities which are involved could be incorporated to the product use case.

10 min

Wes - Is there confusion around this and, if so, what needs to be clarified?

@PSRAMKUMAR

5 min

Other terms requiring review:

• Service

• Building Block

•  

@Wes Brown

5 min

Based on feedback from the various partners, we are going to target the end of March, 2023 for our GovStack 1.0 release.

@Martinez, Yolanda (Deactivated)

@Shukla, Ayush

5 min