2022-11-21 - Sandbox - Weekly Review

 Date

Nov 21, 2022

 Participants

  • @Artun Gürkan

  • @Bert Viikmäe (Deactivated)

  • @Wes Brown

  • @Nico Lueck

  • @Meelis Zujev (Deactivated)

  • @Satyajit Suri

  • @Jonas Bergmeier

  • @jarkkohyoty

  • @Priit Puru

 Discussion Topics

Item

Notes

Agreed

Item

Notes

Agreed

Architectural overview

@jarkkohyoty

approx. 10min

Jarkko explained how we came into such proposal.
Any feedback and clarifications is expected from tech commitee members (weeks 48-49)
Formally the architecture needs to be accepted by Technical Committee

Frontend Framework Decision proposal

@Priit Puru
approx. 10min

UI component library candidates techically evaluated:
Decision to be taken after review with UX/UI working group this week

Priit presented team discoveries what will be presented at UI/UX ws meeting.
Q:

  • @Satyajit Suri asked abou Mobile complience- it will be taken into account at choosing moment.

Use Case 1 → Applied Sandbox User Journey

Applied journey will be ready for review Wednesday latest → who is available and willing to dig deeper with us to provide feedback

@Artun Gürkan @Jonas Bergmeier

@Nico Lueck will send an invitation for people to be attended- review meeting will be open to attend anyone intrested about it.

Backlog refinement and Sprint 2 planning

Team will continue building sandbox hosting environment and will start implementing x-road BB into it
Simultaniously will continoue User Flow designe and Front-end designe.

Feedback and inputs will be given in Slack or directly throug PM

Last weeks topics

 

 

Use case steps, workflows, building blocks

@Artun Gürkan @Jonas Bergmeier will share, approx. 30+15min

Proposal to continue work in separate workshops with @Wes Brown and needed participants

 

Scope Review Session

  • Who presents what?

    • Nico and Jonas/Artun to go through the visualization and scope page how to join the materials

    • To be presented:

      • Main functionality in high level

      • Main user groups

  • Feedback mechanism

    • A separate section on the scope page for feedback

    • New confluence page for each round of feedback

 

Use Case selection

@Wes Brown demonstrating the G2P/unconditional cash transfer use case

https://github.com/akmad/temp-use-cases/blob/main/use-cases/inst-usct-1-unconditional-social-cash-transfer.md

UC now in Wes personal workspace, so will move at some point.

 

BB candidate selection based on Use Case

Which BB WG and BB suppliers to contact?

To be checked once the use case is completed.

 

Demo instance needed?

Shutdown or keep the demo instance of the working group which created a first prototype?

At the moment no need for the demo.

 

A shared understanding of definitions and overview of Use Cases, workflows, and Building Blocks and their relations.

@Artun Gürkan @Jonas Bergmeier

  • Concepts and terminology

  • Use cases - Workflow - BB relationship mapping

    • currently describes the situation well, but subject for change

    • to be included to the sandbox confluence page

    • two selected use case to be mapped for wf & BB

 

User Research

Add task to add and validate user stories with persona representatives.

First task: @Nico Lueck to approach country colleagues whom to approach best

on going

Schedule meeting on project plan/roadmap

Monday 14th of November, Nico to invite.

 

 

 

 

 Action items (last week)

@Nico Lueck will check on how a shared Sandbox calendar can be created
@Jonas Bergmeier Tools used to document FE and UX part
@Artun Gürkan@Jonas Bergmeier create a page on sandbox confluence about the Use cases - Workflow - BB relationship mapping
@Marko Kilpeläinen to create/add the vision diagram to confluence
@Bert Viikmäe (Deactivated) Create deployment diagram v2 with feedback incorporated
@Nico Lueck schedule the two meeting (vision & BB/use cases) for this week.
@Nico Lueck Create BB candidates overview, dependencies and earliest availability
@Nico Lueck To check the date/time for vision/FuncReq page review meeting
@Meelis Zujev (Deactivated) will come back to topic how show the roadmap in higher level 22.11.2022

 Decisions

  1. Copy at least one other person for any gofore emails, to ensure that information doesn’t get lost