Identity and Trust related WGs Future Scope and Relaunch Activities

Objective

Create with key participants and stakeholders a strategic roadmap for Identity, Wallet, E-signature, Consent, (harmonise with Registries) building blocks that outlines both the long-term strategy and the next major releases for these topics.

Whilst initially an in person kick off event was initially planned to drive this, finding dates that worked for a lot of the team was a struggle therefore we look to achieve a similar outcome through virtual and asynchronous working.

How:

Through a 3 phase approach, May through July, where we

Phase

Mode

Month

Identify the conceptual problems that must be solved around the ID space and identify their areas of overlap and contradiction

Virtual

May

Define the strategic roadmap through consensus building on the general features that each building block must follow

Virtual and Asynchronous

June

Finish Proposal Document per BB, a Strategic Roadmap for all ID-related BBs and Launch and promote publicly the strategy

Virtual, in person on conferences participants attend

July

1.png

Specific Objectives:

  1. Remove Ambiguity and be able to clearly articulate the ID building blocks

    1. What they are

    2. How they interact

    3. What gaps exist (e.g. potential future BB’s we may not have.

This is about adding some structure to the existing landscape to aid understanding

Screenshot 2025-04-27 at 14.40.52.png
  1. Increase participation and have a vibrant community developing them

    1. Confident space to work

    2. Increase membership and participation

    3. Be visible externally as to our work.

Roadmap to achieve this:

The 3 phase Approach

Screenshot 2025-05-24 at 20.44.19.png

Phase 1 - Investigation and Understanding (Online)

Underway now and continues through May.

Through online meetings and asynchronous discussions refine the conceptual problems around the ID space and related BB’s identify areas of confusion, areas of contradiction (e.g. recently identified one with Registries BB). Identify possible solutions.

Based on the discussions in Phase 1, have a starting position paper that highlights the existing confusion, and a starter position on how this could be resolved which is shared with the wider active community in Phase 2

Phase 2 - Definition and Consensus (Virtual and Asynchronous)

In order to get the most out of this phase we will encourage discussions and constructive feedback to get to consensus and alignment.

Where issues cannot be initially resolved we will use a virtual “Car Park Board” to ensure they are noted and we will reflect back at key points if we can now address these. The use of the “Car Park Board” is to ensure we maintain a momentum to a solution whilst not ignoring concerns.

Phase 2 has 3 quality bound sprints e.g. each sprint of varying length has a quality gate we will review together before moving to the next sprint.

Through 1-1 interviews we will add an initial set of potential future scope items to our virtual “Brown Paper Wall” during Phase 2 these will be discussed, prioritised to identify draft charters for the WGs.

Week 1: 2nd - 8th June (High level Alignment)

Objective:

Agree Meta-Layer

Diagrams

Text

Explain how BB’s work together

Agnostic of solutions or frameworks

Common Terminology

Date

Format

Purpose

2nd June

Kickoff Meeting - Virtual

Set out overall objectives and timeline

Answer questions

Set out objectives for week 1

Outline Interviews approach for scope items

2nd-8th June

Asynchronous with discussion on nominated group

Review the position paper and suggest changes.

What does it mean for each BB:

  • Can we map them into this

  • Can we identify missing BBs

  • Do we need to adjust any

Compile our Terminology

Start Car Park

2nd-8th June

Virtual

Individual Interviews week 1: David will reach out to people individually to compile a list of things they believe should be considered for the roadmaps across the BBs

Expected Outcome:

Clarity and common terms between BB’s

Start compiling future scope items asynchronously


Week 2: 9th - 15th June (Consistent BB Definition)

Objectives:

Agree definition text for each Sub-BB including any identified new ones.

Define any new terms used.

Date

Format

Purpose

9th June

Retrospect and Task Planning - Virtual

Retrospect:

Review outcome of week 1

Are we in agreement if not what steps are needed

Is there anything we need to Car Park?

Task Planning:

Set out objectives for week 2 of simple definition of every identified BB

Common Terminology


Quality Gate

Are we ready to proceed ?

9th-15th June

Asynchronous with discussion on nominated group (small groups may agree to work together with additional calls)

Draft BB definition for each BB.

What does it mean for each BB:

  • What is the BB

  • What is in scope (this includes future scope)

  • What is out of scope (e.g. we will never consider)

  • What are cross dependencies (e.g. things we expect from other BBs or things we think we should be giving to other BBs)

Update our Terminology

9th-15th June

Virtual

Individual Interviews week 2: David will reach out to people individually to compile a list of things they believe should be considered for the roadmaps across the BBs

Expected Outcome:

Complete initial future scope item gathering asynchronously

Have a definition for each BB

Have defined dependencies

Have a common terminology guide


Weeks 3 & 4: 16th - 27th June (Future Roadmapping & Scope)

Objectives:

Expand our Common Terminology

Identify items for future scope for each BB

Identify any gaps in resources (skills/insights)

Prioritise scope

Populating in Draft Charters

Look for overlaps and commonality

Look at car-park board can any be removed.

Date

Format

Purpose

16th June

Retrospect and consensus resolve any conflict - Virtual Meeting

Retrospect and Consensus:

Review outcome of week 2

Are we in agreement if not what steps are needed to resolve this is expected to be discussion in the call

Is there anything we need to Car Park?





Quality Gate

Are we ready to proceed ?

17th June

Task planning - Virtual Meeting

Task Planning:

Set out objectives for week 3 & 4 to get a future scope roadmap

David to share post-it board of scope items identified and initial mapping where known

Common Terminology

17th-24th June

Asynchronous with discussion on nominated group (small groups may agree to work together with additional calls)

Identify additional scope items and add to post it note board

Map to BB’s those that should fit in scope

What does it mean for each BB:

  • Are there new items not identified

  • Are those mapped correct

  • What is priority

  • What resource is needed

  • Draft a future scope board

Update our Terminology

25th June

Re-group - Virtual Meeting

Review of progress look at what areas multiple BB’s want to look into (can they collaborate).

re-introduce BB charter docs

25-27th June

Asynchronous

populate draft BB charter docs for 2025

27th June

Closing Session - Virtual Meeting

Playback of what we have achieved,

Review Car park and close down any issues needed

Next steps


Quality Gate

Are we ready to proceed ?

Expected Outcome:

Draft BB Charter

Consensus between BB

Draft Future Scopes (circa 2-3yrs)

Gaps identified for specific resources


Phase 3 - Promotion and Progression

This phase is post phase 2 and is focused on how we share what we achieved, gain new membership and move into active progression in working groups through regular meetings.

  • Share with Technical/Architectural Board Outputs (especially Meta-Level and Definitions) July

  • Create some form of output that can be shared both to the wider inside community and the outside community about what we are thinking from GovStack.

  • Launch Call for Participation, clearly call out any specific needs we have identified.

  • Promote GovStack online and at events

  • New Member Induction 1-1 with WG leads/Representatives and Facilitators

  • Re-Launched WG/BBs ratify draft charters and regularly meet.

Participants for Phase 2

Participation is Open to current Active members of the following WGs who agree to GovStack Code of Conduct:

Registries

Identity

Wallet

E-signature

Consent