Agenda

Presenter

Duration

Discussion

• Review pending action items

• Risk register

@Esther Ogunjimi

10 minutes

Technical Risk Register

Update on test plan

• Test plan is delayed because of the building of the mock example for some of the BBs.

• No mock example for ID BB as it requires a developer to develop that

• Consent BB has developed one stub, but still not complete

• Payment BB - relaying on open G2P to carry testing but there is no internal resource to carry out mock example

• Workflow BB - has an example but yet to be tested upon.

Summary: no uniform progress from across BB as regards test plan

Steve - there are two streams of work as it is being stalked in the BB backlog. To identify what are the APIs (first set APIs to be tested), the footprint in the APIs

1. the BB leads to identify and define the APIs - to be done by domain expert or the BB leads

2. Implementing test in marks - requires technical expertise, and sodevlo will support the BB working groups with technical tasks

Jira structure - backlog grooming/sprint planning cadence

@Steve Conrad

15 minutes

• TC should start sprinting in the same cadence as the gofore team

• Set up bi-weekly meeting for scrum of scrums - for all BB teams to connect to plan the next set of work (sprint planning) and review the work that has been done (retro)

• All BB should identify the first set of APIs (some of APIs are oriented around postpartum UC)

• All BB should say that this is first set of API in English

• Set up bi-weekly meeting for the BB Lead for sprint planning and retro

• Ensure BB leads prioritized their first set of APIs

• BB leads should estimate how long it will take to identify and define the first set of APIs

• identify the first set of APIs and document them in the BB specs (in English)

Satya - testing team are blocked as there are less technical capacities to take APIs and build mock examples.

Ramkumar - the cycle of defining the first API has lingered and still we do not have the first set of APIs. There are concern that country engagement team will soon be sending UCs to TC. We should not wait for all APIs to be qualified before testing but start integrated testing for the qualified APIs with IM.

Testing team will support BB teams to write APIs in swagger.

Move qualified APIs to integrated testing; for unqualified APIs which are already defined; get them into testing (API qualification), and for undefined APIs- get testing resources to help write swagger codes

Ingmar

Have presentation/training for API description

Steve

Have clear template and bit of training for all BB Leads

Architecture - discuss scoping priorities for next round of spec

@PSRAMKUMAR

15 minutes

There are two phases of activities runing in parallel;

Phase 1 - Identifying, testing and qualifying APIs - this is ongoing

Phase 2 - BBs continuing to enhance specification. Some of the BBs have identified what they will do in the next phase after the TAC review - this should be evaluated and should sync with Wes (PC Lead)

delegation of consent UC need to be discussed with PC

Wes

Work should that be done needs to be picked based on UCs and not the other way round.

We are not building BBs according to country specific requirements. They are generalized and need to support the requirements with the ability to support when carrying out the implementation.

Need to know the areas in the BBs that require UCs or need to callout UCs that already exist to be able to assist on the product side

Ingmar

hoping for the next phase will have real country UCs that has specific detail and information(e.g., what the actual user information, do they have national ID available). This level of details is required to test registration description.

Jaume

ID BB has the first set of API from MOSIP which are demonstrating the UCs in different ways.

BB status update

• API prioritize tasks

BB Leads

20 minutes

ID BB

Launched the review of the open API. There will be Q&A session next week.

The open API produced will be open to the community.

The prioritized API task are; authentication and Attribute sharing APIs.

Kick off of the review to the community will be done.

Ingmar

Started integration of authentication of user to test the openID connect work

Consent BB

• some progress on test build

• mother-and-child use case prioritized

• still working on increasing the resources for the team

Workflow BB

• Defining the next feature to test which is beyond the initial five APIs- i.e., functional test

• No blocker

• Have five qualified APIs are already defined and are IM compliant

• Have not done end to end testing

Registration and Digital Registries BB

Trying to achieve testing by writing the code, to have something runing.

Add more content to the specifications

IM BB

Gitbook version merged into pdf

Unifying access level API with UXP - under development

Participated in the sandbox planning activities

Need clear description on how to use IM in testing flow

Testing and Integration

@Satyajit Suri

20 minutes

• Looking for support from Alex to complete the entire testing process along with IM.

• working on completing API spec and mock example work

• Consent API testing is carried out for on API - this will be used as an example for other consent APIs

• To complete the mother and child UC, ID two APIs is needed (ID verification and getting ID attributes). Also the consent APIs (creating the consent), digital registries APIs and payment APIs.

• Do not have the most critical APIs to complete the end to end mother and child UC.

PC read out

@Wes Brown

5 minutes

Defining UC format

AOB

• Attending meetings

All

5 minutes