GovStack Building Blocks January monthly meeting

Sandbox

@Nico Lueck

GovStack Sandbox…​

• makes the GovStack approach tangible. It is the key tool to raise awareness and educate people on the benefits.​

• is an isolated, safe environment simulating a small governmental e-service system (reference implementation)​

• encapsulates the business logic and data necessary to represent multiple GovStack (APIs, BB, use cases and workflows)​

• follows the GovStack architectural approach centered around APIs and microservices to help unlock monolithic legacy systems to increase the speed of IT project delivery, leading to more effective and cost-efficient digital governments​

More information on Scope of work, personas and user stories can be found on this page: https://govstack-global.atlassian.net/wiki/spaces/DEMO/pages/85819393  Current activities:

1. Onboarding provider of BB applications​

2. Setting up deployment infrastructure and hosting environment​

3. Finalizing use case flow of first use case: Unconditional Social Cash Transfer​

4. Start building contextual UI of the Sandbox​

Country Engagement

@Martinez, Yolanda

GovStack Country implementation:​GovStack support countries in accelerating their digital transformation through a whole of government approach according to their context & needs .

Link to Country Implementaiton Playbook: https://govstack.gitbook.io/implementation-playbook/

Link to Country Implementation documentation on Counfluence:https://govstack-global.atlassian.net/wiki/spaces/GH/pages/91357207

GIS

@Tarek Rashed

Our progress

• We are coming close to complete the scoping stage, hopefully by the end of this month, our team had screened several candidate use cases and voted to focus on Azure IIS based incident management system because it's country has some sort of emergencies you have to respond to. So to demonstrate the core GIS building blocks function, we are also contemplating or accepting as our use cases maybe in the future. But right now we're focusing on the GIS.

• Our high level logical journey is been split into four major steps

  • how to respond to an emerging

  • how to report an emergency

  • how to dispatch resources to emergency

  • how to manage the incident, and then

  • how to close the case.

• We are now very close to finalize the logical process blueprints and related services in each of these steps and once completed and bitted, we will be moving to the next step, which is related to scenario service calls, in terms of our pin point, I guess our main challenge has been so far engaged all team members. They have been engaged in a way or another but not fully engaged. That has been a challenge to encourage them to be engaged all the way. And we are also trying to bring in some more volunteers to help us.

e-marketplace

@Sujith Nair

Members:

• @Sujith Nair from India

• @Ravi Prakash V

• @Caroline Mulligan

• @Vikash Madduri

• @Umesh Mohanty

• @Mohamed ElGendy

• @Ibrahim Elbhery

• @nsanie (Unlicensed)

• @Rezwanul Haque Jami (Unlicensed)

• @Sohel Rana (Unlicensed)

• @Gavin Hayman

• @Ben Vandersteen (Edu)

Closing the scoping

Wants from e-MArketplace Working Group:

• Suggest any other interesting use cases

• We can get started with the whole sandbox side of implementation for emarketplace that's probably structure we've been struggling in the middle somewhere December in terms of getting use cases and getting a feel of what the e-marketplaces is typically do across the world.

• We're going to pick up some speed in the coming month and reach out to some of the other building block teams as well.

UI/UX

@Laurence Berry

Objective:

• To build specifications for design system that has front end user interface components and elements, workflows that will be used by the different programs or projects or services actually using the building blocks

• Scope: we've broken into 4 phases and we're probably only really gonna focus on phase one and two.

  • Phase 1: front end elements required

  • Phase 2: defining flows for common user journeys

  • Phase 3: guidance out into something that could be

  • Phase 4: GovStack front-end APIs

Wants:

• Want to work with building blocks who are implementing our output on frameworks that building for their building block and also to access their materials that definitely will come handy when you're putting together the the design system because we want consistency.

• We need technical resources to make it easy for the BBs to implement the design system.

• Improve how we engage in our own team, Sprint planning, putting collaboration and bringing everyone together so that we can work on this.

• We will need a front end developer or a designer as well, especially in the last final phases of the of the scope as we mentioned.

@Mathlouthi, Walid @sasi

February technical monthly meeting

All Working Group Leads

@Mathlouthi, Walid

@sasi

@Laurence Berry

@Sujith Nair

@Tarek Rashed

Feb 3, 2023

@PSRAMKUMAR

@Steve Conrad

@Martinez, Yolanda

@Nico Lueck

@Rachel Lawson (Unlicensed)

@Margus Mägi

Feb 17, 2023