Page History

...

• Comprehensibility: We want to go for use cases that are not «too academic», but easily understandable for most
  • Nothing that needs lots of explications and community insights
  • 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
• BenefitsBenefit: 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?
  • X-sectorial relevance: Can we show relevance beyond our own community? E.g. presenting diploma from our sector to outsiders
• 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
  • We should not go for marginal gains, but rather for major steps
  We do not want to compete with existing solutions, but enable new stuff
• Legitimation: We want to go for use cases use cases we have an estalished position in and can easily «claim territory» in some way
  • It should be apparent that our community has experience and a role in this use case
  It should be clear that we are needed here, we do not need to explain our raison d’être
  • 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
  • We do not focus on paving the way for others, but primarily for ourselves
  • 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
  We are not doing research but shaping our own future

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