Introduction from Ramkumar

30

 Ramkumar

Coordinating the cross group meets eg, coordinating dependancies with other groups

BB group goals

• We should observe the different use cases of this building blocks and match them with the needs of the specifications. Think of the the constraints on our BB based on demography and the journey of implementing the bB so that users can have a reference point.

• Think if our BB APIs are compatible to work with other BB APIs.

In the initial sprint 1 we need to identify those that fall within and those that fall outside of our scope. Prioritise the different focus areas in a logical process to work on them as a team. Break down the steps from a use case scenario, to a micro service level that are needed for the building block.

• We will not only build interface elements. We need to build for interactive modalities between the front end and existing BB APIs. 

  Each building block has its own administrative UI, but if they use our UI/UX BB it saves them from creating front end elements. 

  Our goal is to enable people build a front end that is guaranteed to work in multi-modals and with different API systems of other BB specifications. 

  These solutions are key especially if the people using this tool are not programming experts. Also, all BB specifications need to removes heterogeneity that users will face. All bbs also need to be reusable in different circumstances and context. 

Get to know each other

10

 Everyone

Define "what is our BB all about anyway?" for yourselves to share together

15

Laurence

GovStack UI/UX bb space

Define scope of work & expected deliverables

20

Everyone

Discuss best meeting times

5

Everyone

Set actions for the next week

• Collect at least 2 examples each of EXISTING solutions (hopefully open source, but also proprietary) that might comply with your envisioned specification.

5

Everyone