-
Notifications
You must be signed in to change notification settings - Fork 35
pycon 2020 user research plan
This research plan outlines the UX research activities we expect to carry out at PyCon 2020 - including the Packaging Summit, Maintainers summit, the main Pycon and Pycon sprints.
The objective are to:
- identify packaging problems to be discussed at the Packaging Summit
- identify Python Package maintainers research questions about 1) above, so they make good decisions on solving the packaging problems during and after PyCon Sprints
- understand Python community expectations, usage of and issues with pip.
This research will depend on the Packaging topics proposed by the community using this form before the Packaging summit.
If no topics are proposed, <WHAT DO WE DO?>.
The purpose of these discussions are for attendees (package and tool maintainers, distro maintainers, ideally end users) to reach consensus on how to design and implement solutions for the topic/problem.
These discussions will contain assumptions - technical design, implementation, user expectations, how user workflow will work - about how the problem should be addressed. These assumptions need to be validated with users i.e. the people who will end up using the feature/command.
The goals of this study are to:
- identify topics and Python Packaging problems the community want to discuss at PyCon Packaging Summit
- identify research questions to answer
- carry out user research with PyCon attendees to gather information
- provide maintainers with information they can use during the PyCon Sprints
The goals of this part of the study are to answer these research questions:
- What do pip users think its purpose is?
- What expectation users have of pip? (What do you need from pip?)
- What do users use pip for?
- What do users wish they could use pip for?
- What pip commands do you use most and why?
- What pip features do you use most and why?
- If all pip commands were removed, what 1 command could you not live without?
- If pip went away, what would you use instead?
- What is your Python development setup?
- How pip output messages could be better?
- How do you find packages with pip?
- What is the usage of
pip search,pip find?
and to <???>.
We will attend the Python Packaging Summit on April 16th, PyCon on the 17th-20th and then PyCon Sprints 21st-??.
We will setup a "UX Open Space" somewhere in the venue. This will be used as a drop-in location for attendees to talk with the UX Team.
We will try to stay in this space/near-by for the whole PyCon.
The UX Team will bring laptops, web cameras and digital voice-recording equipment.
The web camera will be used to record participant's face and audio. Alternatively the voice-recording equipment will be used to record the discussion audio.
If participants bring their computers, they will be able to use them to demonstrate their dev. setup during discussions with the UX Team.
We will ask participants for their consent to 1) record video, 2) record audio during the research.
They will be asked to complete an online research consent form.
We will publicise this research with PyCon attendees by:
- advertising it:
- creating a "UX Open Space" at PyCon where people can drop by and be interviewed by the UX Team.
For this research we will select participants from the Packaging summit & PyCon attendees:
- package maintainers
- Python users
We will recruit research participants at-random during PyCon, and by inviting people to speak with us.
- Each topics will be discussed for 30 minutes. The UX Team will either observe, or ideally help facilitate these discussions.
We'll document:
- problem/topic discussed
- decisions made
- identify assumptions
- identify questions that come up and need to be answered
- UX Team will then identify user-related questions maintainers need information about, and then create research questions. These will be used during PyCon to interview users.
If the questions aren't clear enough, the UX Team will work with the people who've attended the discussion to make these into research questions.
Some questions could be - what do you expect to happen [with this feature/command], how/if do you expect to use [this feature/command], here's how I expect this to work for me and other questions that need to be identified, etc)
- These questions will then be used during PyCon to interview package maintainers, and Python users.
These sessions will be 30 minutes.
This research will be exploratory to understand pip users expectations but will also gather quantitative data about pip command usage.
We will carry out research with everyone and will then categorise those users into groups.
All participants will be asked the same questions.
These sessions will be 30-45 minutes.
To be worked on:
- Interview PyCon attendees.
UX Team interviews participants (users of packages and package maintainers) at PyCon using the quesions identified in step 2 above. The output will be user requirements/expectations that can be used to inform the work on the problem during the PyCon sprints (or after).
-
The interview then need to be analysed and some output needs the be produced. Questions:
-
what format does that output need to take?
-
some information about the users interviewed, their background
-
GitHub issues
-
User stories
-
more?
-
20th-23rd April (PyCon Sprints) (partciipant recruitment: in teh early days there will be more "end-users" attending. Towards the end, the people left will be more invested - e.g. maintainers, long time contributors)
-
The package maintainers will take the output from step 5 and use it as input to their sprint work.
-
(optional) If there is a possilbilty to do some usability testing of early "prototypes" of the work from the sprints? The objective would be to find users at the sprints to test the prototypes with
-
Conduct interviews with package maintainers and end users about other topics too
- identify and talk to new 1) python and 2) packaging, contributors (roving reporter style)