2023-01-25 - Product Committee

Presenter

Time

Notes

@Wes Brown

5 min

• Rachel: further discussions still needed on where documents/materials need to be stored -gitbook, before starting tech teams documentation training.

• Ayush: still working on the master directory with Yolanda and Ramkumar. It should be done in two weeks.

@Shukla, Ayush

10 min

Ayush’s presentation:

• Each country specific project has its own page on jira.

• Under project pages you will find the confluence page specific for that country engagement.

• On confluence - under the GovStack space, you will find the country engagement page where you can find general information in regards to country engagement i.e. county implementation framework, info on where meeting notes are found, where activities are being tracked on Jira etc.

  • There is also a table that lists countries being engaged, team members involved, use case documentation on confluence etc

  • Stages of the country implementation journey deck is currently being reviewed, once it is finalized it will be uploaded on confluence.

• Ramkumar: he and Steve are putting together a template project for a use case - from a Jira perspective - to integrate the work that is happening between the country engagement, product and technical committee teams, in one flow. They will coordinate a meeting Wes and Yolanda to develop a harmonized system between all workstreams.

• Yolanda: recommends that Ramkumar and Steve refer to the stages of implementation journey designed in the country engagement work to ensure consistency in documentation system. Important to have a standard based system of all the tools and methods being used in GovStack.

• Wes: Streamlining how we do things and track them on Jira is important.

@Sainabou Jallow

15 min

Draft ERP Use Case: GitBook

Sourced from GIZ/ITU EPR Rwanda Use Case (GIZ SharePoint)

Use Case General Comments

• Yolanda: important to include the links to the GovStack playbook and country specific resources to the generic use cases, so that any user can access rich content and resources of how the specific use case is being run in a specific country i.e. the EPR implementation in Rwanda. This will be helpful as we reiterate the use cases.

  • Yolanda and Ayush to develop a proposal of how to link the country specific resources on gitbook in order for these respective links to be embedded in the relevant product use cases.

• Wes: anything that we link to the use cases should be public and similarly versionable - similar to everything that is linked in the product use cases and specs. This is to keep all changes in sync.

• Margus: Lessons learnt from the implementation projects and having regulatory procedures and processes. Create additional implementation best practices from change management and regulatory reform perspective recpomendations.

  • i.e. the information mediator, would beed to have additional national wide regulatory ramification which will ratify what is the basis on data exchange between the government entities. Have recommendations and best practices that can be shared with countries.

• Wes: we could have a header section in the use cases where we provide recommendations/ references of best practices that would be relevant for countries.

• Yolanda: There are 3 user journeys that are a part of the Rwanda digital service. Need to define as a team, the timeline and best way to create functional prototypes of the user journeys.

  • Have a series of workshops planned with Rwanda in the coming weeks to define architectures of the prioritized services, and implement functional prototype that is designed with the country. Need time to test specific country specific use case tested first.

• Wes: what the building block leads are supposed to be building is not the country specific use cases/user journeys. They need to be working on generic use cases, and the sandbox should be aligned to generic use cases, not country specific ones.

  • The goal of the product use cases is to be generic enough for countries to facilitate the functionality needed/required.

• Ramkumar: recommends that building block leads still be involved in the country specific use cases. For them to observe and be more involved.

• Taylor: echos Ramkumar’s point - work of technical and product committee should constantly be informed by the use cases. Real imnplementations should inform the specifications. We need to figure out if GovStack should do the particular use case implementation in a country.

• Sarah: reference implementation should be iterative and feedback to the generic use cases. Once use cases are implemented in country then all that information should be brought pack to reiterate the generic use cases.

• Wes: general use case should be representative enough for the build block specs to be applicable.

• Margus: whatever is happening in the implementation process should reflect in the building block specifications. If we do reference implementations then we try to solve a couple of problems with a couple of products on the ground and try and compare what can be done. Issue of credibility if we do not do the country implementations.

• Steve: how deep are we going into the implementation work. Need to be clear about what are the scope of the functional prototypes, selecting specific tools and being vendor agnostic.

• Yolanda: have an area for country specific functional prototypes used for country digital team to learn.

ERP Comments

• Sarah: what are the generalized boundaries. Some definitions with a use case, who is it targeted at and what are the producers.

• Yolanda: have a round of iteration of the EPR use case - need to include other building blocks: UX UI, digital signature etc,.

• Wes: all can make comments on gitbook via comment or send an email for input and comments. Country user journey being turned into a use case. Then next week hand it to technical team for comments and input.

@PSRAMKUMAR

10 min

• All are asked to review the terminology in gitbook and provide input - GSCIJ-30 Added new terms and deffintions to Terminology section of Playbook

@Wes Brown

5 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 / @Martinez, Yolanda (Deactivated)

15 min

@Moritz Fromageot

20 min

There was a lengthy discussion in the GC Meeting. Need to agree on way forward (Timeline, Outputs, Resources)

10 min

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

@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.