Package: Solution Validation around the Remote and Virtual Repository UI
What's this issue all about? (Background and context)
We are completing an investigation issue focused on understanding and planning the technical implementation of remote and virtual package repositories. Working in conjunction, we have been putting a UI to add, remove, and manage remote and virtual repositories.
I'd like to plan and execute solution validation utilizing the UI to understand if we've successfully captured the needs and have a sound solution to move forward with.
What are the overarching goals for the research?
Determine if the proposed solution for remote and virtual repositories meets user's needs, and confirm that the proposed UI would enable users to manage these external repositories.
What hypotheses and/or assumptions do you have?
Users, especially users who are part of larger organizations, will appreciate being able to pull packages from an aggregated list of repositories, whether they're hosted on GitLab or external and 3rd party package registries.
The secondary assumption is that users will understand the proposed user interface in relation to these repositories.
What research questions are you trying to answer?
- Will our proposed solution meet the need we discovered through problem validation around remote and virtual repositories.
- The proposed user interface is understandable for users to easily understand the feature, create new remote and virtual repositories, and be able to manage a robust setup.
What persona, persona segment, or customer type experiences the problem most acutely?
DevOps, Sr. Engineering, or other system architect level user in an organization utilizing packages in multiple places.
Open question - @trizzi is there a particular persona you would identify here?
What business decisions will be made based on this information?
- Does the proposed solution fit the need, raising confidence in the decision to build out this solution?
- Is the proposed UI easily digestible, explain the power of the feature(s), and aid users in managing more complicated package registry setups?
What, if any, relevant prior research already exists?
Who will be leading the research?
What timescales do you have in mind for the research?
I'd like to execute on solution validation in 13.2. This assumes that the proposed UI Design is completed in 13.1 after rounds of peer feedback among the team.
Relevant links (script, prototype, notes, etc.)
-
Create a discussion guide outlining questions and tasks -
Create a prototype that users can use to complete tasks related to the proposed solution -
Open a recruitment request for 5-8 users to perform validation. -
Create a screener survey in Qualtrics -
Perform user interviews -
Synthesize data in Dovetail