Design Sprint- License Management across Multiple Instances
Sprint Goal
The aim for the sprint is to design a license model that enables management of distinct billable users across multiple production and non-production instances.
Target users
A owner or admin of multiple self-managed instances who will add and remove users, or review users across multiple production and non-production instances.
User goals and JTBD
- How can I efficiently add/remove users to give them access to one/two/more instances?
- How can I see how many users I am paying for, and if they are being billed for multiple instances?
What else do we know about the JTBD scenario?
Scope
- Cloud License enabled for MVC
- Offline, air gapped environment post MVC
User research
- What user research can we reference to inform the sprint?
- What questions about users do we need answered in order to confidently move into design?
- How does this work currently?
- What feedback do we receive from users?
- What's a typical instance/user size?
- How often and what kinds of users need access to multiple instances?
- Do they have the same or different roles?
Design sprint reference docs
Design Sprint preparation
-
Finalise participant list - decider
-
Convert this issue into Epic to manage each step - facilitator
-
Create sync meetings in calendar and invite all participants (deadline: [date]) - facilitator
-
Prepare material and tools (eg. presentation templates, Google folders, Instructions videos etc) and Mural board - facilitator
-
Finalize Agenda - facilitator
-
Run a test with material and tools - facilitator
Design sprint participants
- Tim Noah -
facilitator
- Teresa Tison -
decider
/stakeholder
- Matt Nearents -
participant
Design sprint steps
-
Step 1 (async): Completion Date: TBD
Gather user research and add notes to the "problem" section of the design sprint mural. (link TBD) Each participant will speak to 2 dev leads in GitLab to learn about their problems and add notes to the ["the user's problem" section of the design sprint mural]-
add sub-steps and notes here
-
-
Step 2 (async): Completion Date: TBD
All participants read the notes in add link to Mural or notes doc-
Participant Names (optional or required)
-
-
Step 3(sync): Date: TBD
We'll meet to discuss our findings, refine the problem and proceed to the "challenges/themes" part of the [design sprint mural]. -
Step 4 (async): Completion date: TBD
Lightning demos — each participant finds good examples of inspiration related to how to solve this problem, adds screenshots and notes about what particularly they like. Link TBD. Write a message in thechannel name
channel on Slack when you added your screenshot and notes so others can take a look.-
Participant Names (optional or required)
-
-
Step 5 (async): Completion date: TBD
Concept sketching — each participant comes up with a conceptual sketch (or two) for the challenges voted in step 2 and adds them to [the "Concept sketching" part of the mini design sprint mural].-
Participant Names (optional or required)
-
-
Step 6 (sync): Date: TBD
We meet to discuss the sketches, give each other feedback, vote and do another quick iteration if needed. -
Step 7 (async): Completion Date: TBD
A designer will take over and prepare an early-stage concept/prototype with an aim to show it to identify some potential testers. -
Step 8 (sync): Completion Date: TBD
Hold calls with the testers and document feedback. (Add recordings here) -
Step 9 (async): Completion Date: TBD
Discuss feedback with sprint participants and plan for revisions -
Step 10: Product designer to finalize design vision and begin conversations regarding MVC breakdowns.
Edited by Tim Noah