Activities
Last updated
Last updated
Use case communities should work collaboratively to define use cases by:
Conducting to help understand the problem more deeply, identifying qualitative and quantitative insights which evidence the need for the use case. This may use existing insights and reports or explore needs through direct engagement between individuals and organisations representing the use case community, and the users they are designing for.
Completing that identify the gap between the current (problem) state and desired (goal) state.
Who are the users that the use case impacts?
What is the nature of the problem?
Why is it important to address?
What impact will addressing the problem have?
Use case communities can prioritise use cases using the , if required, due to the number of use cases identified. The matrix provides a means to prioritise use cases against .
Once the viability of a use case has been agreed, a plan can be created to outline the roadmap for its development and implementation through the following steps:
Define
Define SMART objectives
Define SMART KPIs
Define the needed to deliver your SMART objectives
Identify what a (MVP) looks like
Identify the initial pilot publishers and/or users of the data
Outline the for the use case
Create a timeline for mobilising the use case