20260429 Use case prioritisation and planning

The approach to prioritise use cases was discussed on 5 Feb 2026 and the principles are copied below.

Context

As the community of NRENs within the GEANT community, we have been involved in «identity stuff» for decades. One of the most visible services it produced is eduGAIN. That is where we come from.

The most important stakeholders we do this for are:

• Students
• Researchers
• University administration

Our specific focus in our GEANT collaboration was generally speaking:

• Making local stuff interwork – often interfederating national federations
• Setting standards for this to work sustainably – with a specific focus on the international research and education community 
• Establish collaboration channels and governance structures – mostly through the GÉANT organisation and projects
• Emphasis on Europe, but reaching out to other regions for global interoperability – where possible with similarly scoped regional players

Scope

Let’s narrow down the wallet use cases we would like to work on:

• We are not pushing wallets for the sake of the wallets, but only care for wallets as long as they are doing interesting stuff for us
• To create focus, let us concentrate on the X most interesting ones, where 3 < X < 10

Proposed prioritisation principles

Some criteria for prioritisation of wallet use cases:

• Comprehensibility: We want to go for use cases that are not «too academic», but easily understandable for most
  • Community: Suitability to communicate the use case to NREN staff and NREN stakeholders
  • General public: Suitability to communicate the use case to the general public
• Benefits: We can easily describe the added benefit with respect to existing solutions we have in place or easy to grasp benefits for problem statements we did not address so far
  • General benefit: We can explain the benefits in easy language understandable to NREN staff and NREN stakeholders
  • Community benefit: What does it bring explicitly to our community?
• Innovation: What makes this use case innovative?  
  • Enabling: why was it not possible so far?
  • Outlook: What could come next
  • Disruption: We can explain the change or disruption it introduces to existing solutions or approaches
• Legitimation: We want to go for use cases we have an estalished position in and can easily «claim territory» in some way
  • Existing footprint: We can easily point to existing services or other achievements in our community relevant in the context of this use case
  • Strategy support: We have supporting statements in our GÉANT strategy or those of NRENs we can make reference to
  • Community benefit: We can easily point out benefits to our NREN stakeholders (even without explicit GÉANT/NREN service vision)
• Product or governance vision: It should be a use case where there is some future role in running it for us on GÉANT/NREN level
  • Service improvement: We can easily point to improvements achievable with existing activities or services within our GÉANT community
  • Service roadmap: We can easily point to improvements achievable with envisaged new services or activities within our GÉANT community
  • Governance support: We can easily explain the benefit of our GÉANT community governance structures to the use case

Existing collections of use cases

Use cases used in GN5-1: https://wiki.geant.org/x/WgeLKg (most relevant ones taken up in the GN5-2 collection)

Use case collection of GN5-2: https://wiki.geant.org/x/OwHbRg

Prioritisation approach

1. walk through and discuss the selection criteria above
2. start with the list of use cases we have from GN5-1 and GN5-2, which are all on our wiki and assess them according to the criteria from 1.
3. Select the top X use cases for further consideration
4. Quick discussion on each of them to come up with an initial action plan

List of use cases considered for prioritisation

UC 1, 2, 3, ...

Template action plan per prioritised use case

• What would be the perfect outcome in this use case?
• How do we get there?
• Next steps