Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Meelis Zujev (Deactivated)Nico Lueck Satyajit Suri Jane Rose Anthony Kadi Külasalu Simon Eyre Jaume DUBOIS Mauree, Venkatesen Aleksander Reitsakas Vikash Madduri PSRAMKUMAR Sagar Samag

Meeting Recording

https://ituint-my.sharepoint.com/:v:/g/personal/vikash_madduri_itu_int/EdLyGWDko_xHhaTbOFRGASQBhRAnd9jZElbVTY2r4Jg1YQ?e=flowdB

Agenda

The agenda for the first meeting is as follows:

  • Quick progress update and sharing from each of the 4 partners - Sandbox (Gofore), Pay BB - MIFOS (Mifos), IDV BB - MOSIP (Technoforte), IM BB - XRoad (Nortal)

  • Sandbox team to discuss the USCT use case implementation progress

  • Discussion on issues needing the support of the BB partners

  • Shared understanding of key alignment requirements between BB implementations and Sandbox for the USCT use case

  • Identified action points and plan for alignment of Sprints for USCT use case implementation

  • Schedule for regular alignment meetings for the next 3 months.

...

Topic

Discussion

Introductions

Quick progress update

Mifos - completed Sprint 1, Pay BB - MIFOS (Mifos):

  • completed requirements gathering and initial prioritization

  • completed Sprint 1 (8 sprints in total)

  • Sprint 1 focussed on tasks related to implementing Mifos in Sandbox

  • Sprint 2 - focusing on ID mapper

Nortal - on boaring IM BB - XRoad (Nortal):

  • on boarding completed, about to finish Sprint 1.

1st milestone -

USCT use case implementation

  • currently working on 2 key milestones - setting up XRoad and implementing the PubSub messaging functionality

IDV BB - MOSIP (Technoforte)

  • completed Sprint 0 - requirements study completed and sign off done

  • sprint 1 almost complete - setting up the dev environment

Sandbox (Gofore):

  • completed the set up the sandbox infrastructure

  • approached and discussed with BB partners as well as UNCTAD for the happy flow (MVP) case of the USCT demo

  • USVT demo front-end work in progress

USCT use case implementation

  • aim is to design a MVP with happy flow case for the USVT use case

  • demonstrate the Govstack concept and usage of BB applications

  • challenges faced - it is not possible to build the happy flow using the existing APIs provided by the BB applications (Mifos and MOSIP), as they are not yet Govstack compliant

  • Gofore (Meelis) showcased the happy flow process diagrams

  • need to identify the minimum contribution required by the BB partners to adapt their applications to work with the MVP scenario

  • Sandbox team has mapped all the requirements as well as data sets for the USCT MVP, especially the requirements for the APIs

  • Need to assess how these requirements can be aligned with the BB providers current work plan, so that the APIs as required by the MVP can be made available to the sandbox

  • Nico mentioned that the MVP approach is a desirable as it gives a good opportunity to test the BB applications on a small scale before the final product is implemented

Issues needing the support of the BB partners

Key alignment requirements between BB implementations and Sandbox for the USCT use case

  • The collaboration required to achieve the USCT use case will be a good practice case to achieve the outcomes of the Govstack project going forward. Hence, the BB partners are requested to extend their full cooperation towards supporting the Sandbox team in implementing the USCT MVP

  • BB partners need to review the happy flow process diagrams and the data inputs. Vijay spoke about the account mapper seeding requirements that are currently depicted differently in the MVP process flow compared to the flow that is being envisaged as per the Pay BB specification.

    • Needs discussions between Sandbox and Mifos team to sort out the requirements related to the functional ID, account mapper, etc.

Action points and plan for alignment of Sprints for USCT use case implementation

  • BB partners to review the documentation on the MVP process flows and data requirements - Minimum Viable Product (MVP) eg. Happy Flow - Demo/Sandbox - GovStack Wiki (atlassian.net)

  • BB partners to provide information on what customization or changes will be needed from their side to meet the MVP process flow requirements during the next meeting

  • Plan for technical working sessions with the BB partners and Sandbox for mapping the customization requirements

Schedule for regular alignment meetings for the next 3 months

  • Next meeting planned for Tuesday, Apr 25 (10 AM CET).

✅ Action Items

Action Items

Responsible

Date

Mifos and Technoforte to discuss their plan for addressing the MVP requirements.

Mifos

Technoforte

Apr 25.

 

⤴ Decisions