User Research X Agile Product Devlpmt - The Research Backlog 3/4 - Deepstash

User Research X Agile Product Devlpmt - The Research Backlog 3/4

Backlog content

Squad/Tribe/Area — which squad/tribe/area would this work fall under?

Key stakeholders — who are your key stakeholders for this project?

Research question — what’s the question you’re trying to answer?

Type — is this evaluative or discovery research? Keeping track of this over time, will help you to ensure there’s a good balance.

What’s involved? — what UX research methods could you use to answer the question?

UX Researcher Effort — how much effort will it be for you to complete this research? 1 = Low Effort (e.g. days), 2 = Medium Effort (e.g. weeks), 3 = High Effort (e.g. months).



Managing Research and feeding hypothesis and areas to test into a regular research cadence are critical for mature user experience teams and products



MORE IDEAS FROM Backlogs: The secret to managing user research

User Research X Agile Product Devlpmt - The Research Backlog 1/4

What’s the process of creating a backlog?

Step by step process:

1. Run a workshop with your team/s to first capture and prioritise research questions.

2. Using the template, move the identified research questions into the “Backlog” section. New research questions can also be added as they emerge.

3. Starting with the high priority questions, try to fill out as many of the columns as possible

4. Based on the importance and effort estimates, pull the research questions that you are confident you can deliver that month (you can change this to weekly/quarterly if needed) into the “Monthly Backlog”.



User Research X Agile Product Devlpmt - The Research Backlog 2/4

5. Set up a regular meeting (Every two weeks, or monthly) with you key stakeholders (Product, Design etc.) to review the Monthly Backlog and confirm what the high priority projects are.

6. Once you pick up a research question, move it into the “In Progress” section

7. As you progress with the project, you can update the “Status” column accordingly to keep stakeholders informed e.g. Planning, Testing, Analysis, Reporting

8. Once the project has completed, move it into the “Completed” section. You may wish to add a link to your final report in the “Status” column.



Importance — how important is it to answer this research question? Think about the business and customer impact — you may want to rely on the POs to guide you on this. L= Low importance, M = Medium importance, H = High importance.

When is it needed by? — Is there a deadline for this work?

Who/what else could we rely on? — It may make more sense for another team to pick up this research question e.g. Analytics, Customer Insights.

How much do we know currently? — What previous research has been done? Are there insights from other teams/sources which we could use to help answer this question.



Deepstash helps you become inspired, wiser and productive, through bite-sized ideas from the best articles, books and videos out there.



The types of questions that you’re going to get asked are going to be completely dependent on the client, your job role and the project that you’re going to be working on. If going to be working on a project where you’re going to be expected to do a lot of user research and a lot of stakeholder management, then you’re going to get asked questions that relate to “how you work with stakeholders, what your user research process is about.”



What types of questions can you expect in a UX Design Interview?



Agile mindset

Agility is the ability to be quick and graceful. Agile mindsets focus more on core values such as: Respect, Accountability, Collaboration, Being adaptive to change, learning cycles and improvement.

An Agile mindset helps to easily overcome obstacles and not get stuck when unexpected events happen.




1. Planning Poker: All participants use numbered playing cards and estimate the items. Voting is done anonymous and discussion is raised when there are large differences. Voting is repeated till the whole team reached consensus about the accurate estimation. Planning poker works well when you have to estimate a relative small number of items (max 10) in a small team (5-8 people). Tip: try to keep the voting between affordable numbers. Maximize the highest card to 13 points. More on planning poker via this link. 

2. T-shirt Sizing: This is a perfect technique for estimating a large backlog of relative large items. Especially when you have several concurrent scrum teams working on the same product. Items are estimated into t-shirt sizes: XS, S, M, L, XL. The decision about the size is based on an open and mutual collaborative discussion. This method is an informal and quick way to get an rough feeling about the total size of your backlog. More about T-shirt size estimation is here.

3. Dot Voting: When you are faced with a relative small set of items and in need of a super simple and effective technique to estimate you can use Dot Voting. This method has originated form decision making and you can use it for estimating. Each person gets a small number of small stickers and can choose to vote for the individual items. The more dots is an indicator of a bigger size. Works well in both small and large group. You have to limit the number of estimated items. More on dot voting here.

These are different methods you can use to make agile estimation more efficient and an inspiring team effort. Please share your experiences with this below in the comments section.