Page Comparison

Presenter

Time

Notes

5 min

• Mastery document: maybe Rachel can take document as is an put it on Confluence. The master link is floating around - link can be found here. Ayush is waiting for more docs to be more from google doc to Confluence.

  • Take the document as is.

• Valeria: has been tagging people from the team. She has already revised information mediator and has tagged Alexandra. Has tagged others to follow up on this. Almost done with revision of specs.

  Needs more inputs from others to understand specific points.

  Having issues getting in touch with others on

  Ramkumar: live master directory link is ready. Ayush will update the link once the remaining documents still on google drive have been moved to Confluence.

  • Suggested that Rachel Lawson (Unlicensed) could support to upload the master directory onto Confluence.

• Valeria: Almost done with the general revision for each of the BB specs - the information mediator, registration etc.

  • Has been tagging the relevant BB leads for input and clarification needs via Jira. General hurdle is getting responses from some leads even via slack.

Sainabou Jallow

15 min

Draft Use Case: https://app.gitbook.com/o/pxmRWOPoaU8fUAbbcrus/s/YLLEfCKTnmzAMDSDzJJH/product-use-case/urb-1-online-building-plan-approval-system

Margus: registering a user - should not happen - in ideal case, everyone should have a single system. The new issuing service.

Overview

Interactive feedback session facilitated via Miro board: https://miro.com/app/board/uXjVMfs6qOg=/?share_link_id=451717494735

Feedback

Step 2: Registration

• Margus: More clarification needed if this step is mimicking the process of registration building block steps - a generic process that is applicable in any kind of registration process?

• Margus: In the whole of government approach, to register a user should not happen because in an ideal case, everybody should have a singular digital identity - either from the certificate authority or the population registry. There should be in place a single system.

  • In this instance, issuing a username and password to establish certain services or start using certain services should not be a step. However aware that the current reality is different.

Step 4: Data Verification and Validation

• Ramkumar: The description assumes permission has already been granted to access and share applicants data (legal person/legally registered person/entities). This can cause privacy issues especially for businesses.

  • This step should clarify and ensure permission has been granted from applicants. If it's a legal entity, there'll be an authorized person who has to officially give permission to share the relevant records of the organization.

  • This step seems out of order - makes more sense to follow the unconditional cash transfer steps order. Could be moved to step 3.

• Margus: Information mediator should be added as an additional BB - responsible for data exchange needs and verification processes.

Step 5: Review

• Ramkumar: Name of step could be changed to Eligibility Check to align with the terminology used in other use cases.

Step 7: Ongoing Case Management

• Sarah: There should be a different treatment for complaints which requires a different process that is outlined here. Addressing complaints should have a separate step as it also differs to monitoring and evaluation.

• Margus: from the registration perspective, change requests and disputes can be addressed in the same process via a task management system to address disputes or amendment requests.

Additional steps to incorporate

• Meelis: This use case seems to provide only a half service. If the aim is safety and sustainability at state and municipality level, then it should include a process (similar to application) - which validates the quality and accuracy of the building plan post construction. If the aim is to pilot a small part of a full digital service then it is OK, but is should be implicated at least.

  • Sarah: Based on how the product use case is currently defined (single generic process), the current steps are enough. But if we're thinking about it from a service angle/end to end service delivery, then we could add this step. Need to officially decide how we are defining use cases as Govstack and then keeping that consistency throughout.

• Ramkumar: A separate step should be added on method of issuing the permit. Maybe requires generating a new ID, communicating with different parties - informing relevant individuals/stakeholders of the issuance.

  • Messaging BB should be added.

  • Issuing of the permit could be called enrollment. This process is similar to the step in the unconditional cash transfer use case.

• Sarah: Add a cancelation step outlining process of when an applicant who started the application process wishes to cancel the permit request.

General use case format feedback

• Sarah: Likes the visualization depicted on the Miroboard. We should consider displaying visuals in the use cases on Gitbook.

  • A visualization for each use case step. It could be embedded within the use case pages itself.

• Ramkumar: We should figure out how to incorporate capabilities. If we can standardize a generic registration process/template. Offer registration as a generic capability.

  • Then for the next use case, before working on the detailed outline from scratch, we can first check how its different from the standardized use case steps, and what additional requirements are needed. If the process is similar and generic then instead of creating a whole new use case document, these subject domain matters can be included as example implementations for i.e. registration, payment etc.

  • Creating a standard template for these capabilities and adding example implementations per subject matter.

Nico Lueck

15 min

Short PPT Input and Proposal

Question - where can we build up the ecosystems and get in touch with service providers.

Overview

• Focus is addressing the private sector side - how can we build this ecosystem

  .

  • We could do a roadshow explaining GovStack and ask local systems to take up GovStack.

  • Guidance of business aspects - we need to know what are the value production for vendors and SIs.

• Would it be a valuable proposition to

• Challenge is value proposition to private sector actors for GovStack

  • For some products we have

• Ramkumar: comms and engage/incentivize system integrators and vendors to use the GovStack products once they are available.

• Feedback from PC members requested on how to plan activities/ implement the following approaches to get private sector actors on board for GovStack:

  • The team can map/ outline for each product, its the value proposition - with vendors and SIs in mind.

  • Organize a roadshow in different countries i.e. Djibouti explaining GovStack and asking local system integrators to take up GovStack.

Feedback

• Ramkumar: The Comms team went around collecting data from everyone - how to position GovStack What is the value of each product - specifications, and its value proposition. Might be worthwhile to review it.

  • Need to be careful with the usage of the terminology ‘product’. 1. specifications, 2. test cases and harnesses, 3. sandbox and

  example implications,

  • its example implementations/prototypes, and 4. content and tools - capacity building and resource training.

  • We could each GovStack product to specific capabilities For this capability (i.e registration), these four GovStack complying products can be used for registration.

• Sainabou: Organize GovStack relevant hackathons to engage the private sector.

  • We engaged SIs for the marketplace research work, summary of these discussions can be found in this report (pg. 13).

5 min

Status Update

• Review EPR Use Case (

  Jira Legacy
  server System JIRA serverId f5c6bdaf-d23e-347d-a1e8-579e20a81dda key PRD-112

  )

  • Goal is to incorporate feedback received today from Yolanda.

• Setup Online Construction Permit Tasks (

  Jira Legacy
  server System JIRA serverId f5c6bdaf-d23e-347d-a1e8-579e20a81dda key PRD-115

  )

• Compile Online Construction Permit Documents (Epic Required)

• Identify/Invite Country Representatives (

  Jira Legacy
  server System JIRA serverId f5c6bdaf-d23e-347d-a1e8-579e20a81dda key PRD-117

  )