2024-01-10 - Product Committee

5 min

@Farina Owusu

10 min

https://govstack.gitbook.io/sandbox/follow-methodology/govstack-design-sprint

Comments

• Ramkumar: Is this just for the simulator?

  • Farina: This could be applied outside of the context of the sandbox/simulator. The process can be used more generally and is mainly focused on the front-end design.

• Steve: How does this link into the country implementation playbook and the UI/UX Guidelines?

  • Farina: This can be linked

• Wes: Where is the Service Blueprint defined?

  • Farina: This has been defined as part of the country engagement work (it is part of the country implementation playbook)

• Wes: This design sprint seems very in-depth for a single service but it may be helpful to guide how to incorporate these ideas into designing a digital system

  • Farina: It would be great to extend this idea

  • Ramkumar: It seems unlikely to be able to do this well within just 5 days. The simulation can help accelerate this. Need to be careful about the use of specific terms like “service” and “mirco-service”

Terminology: https://govstack.gitbook.io/implementation-playbook/govstack-implementation-playbook/3-terminology

@Wes Brown

10 min

Is this needed? Yes!

If it is, what should the Service Blocks look like?

• Wes: Similar to Use Cases, text-based, multiple-steps

• Ramkumar: Would a service block be for single or multiple use case steps

  • Wes: I think it could be single or multiple, depending on the service block

• Farina: When would people interact with a Service Block?

  • Wes: Two ways - 1 - From the use case, 2 - when creating new use cases

• Ramkumar: We should define the properties of service blocks. Things like:

  • Abstraction of specific BB process

  • Reusable

Who should own this work?

• Wes: This feels like an extension of the use case and could then be owned by the PC

• Ramkumar: The technical components would be in the BB/TC, high-level by the PC

Questions

• Farina: What is the difference between a Workflow and a Service Block? Would Service Blocks also include technical functionalities?

  • Ramkumar: The service block would replace the workflows

  • Steve: Some of the workflows are too broadly defined, Service Blocks should be more restrictive. Service blocks should contain technical functionalities

• Wes/Ramkumar: Should the service block reference down to the BB APIs?

  • Wes: This was an issue with the example implementations, can we just reference the BB workflow instead?

  • Ramkumar: Maybe it is enough to just reference the BB services that are being used

  • Steve: A gap would be inter-BB communication. Maybe high-level sequence diagrams would be enough?

@Farina Owusu / @Wes Brown

30 min

Next meeting is in two weeks (US holiday next week)

Updates from:

GIZ, Estonia, Dial, ITU