We have a small dev team where I am the sole UX designer. So as everyone knows, we can identify UX design issues with various method, e.g., via heuristic evaluation and usability testing. Furthermore, this is often an iterative process.

So for example, if we conduct a usability test, we can use google drive to share the findings. However, if we start to conduct more tests and other types of evaluations, we can up with too many separate documents and it can be troublesome to keep these up to date (what has been fixed, etc.)

I am interested to with what up methods/apps have other teams used to share the UX findings within the dev team and how do you integrate these methods with agile project management tools.

closed as primarily opinion-based by Devin, JohnGB May 6 '16 at 17:20

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.

  • Are you co-located with your dev team? – SteveD May 6 '16 at 9:31
  • We are co-located 3-4 days per week. – jakapo May 6 '16 at 11:57

Google sheets have worked well for my team in the past. We listed each individual finding in a single row, making sure it describes a single item. Then in the following columns you'd include more details such as possible trade-offs, reasons that might have caused the issue, even ideas for improvements (as they often come during while you're testing). You can also include columns that capture number of times a particular issue occurred, its severity, priority etc. As the number of studies grow you can start adding new sheets to the document, and later start creating new documents and folders.

I'd be against using a separate software just for capturing UX findings. Your development team will be reluctant to use it. And if they do they will gradually stop visiting it over time. You probably already use Google Docs for other things so there should be less friction.

In terms of integrating this into agile processes. I think it'd be good to schedule for occasional UX Review sessions (similar to Design spikes) to go through the most recent studies, discuss the issues, assess collaboratively their severity, uncertainty, and possible dev / design costs. Based on this information the product team should formulate stories that get integrated into the following sprints.

One extra note. Many usability experts recommend inviting people from outside the UX team to usability studies, just to observe. Especially people that are later involved in working on solutions to the identified problems (e.g., devs).

  • Thank you for your answer! I had also been thinking of just making a better Google spreadsheet. :) – jakapo May 9 '16 at 1:05
  • Also, what we are now thinking is to use Github issue list. It could be easily integrated with other agile tools, but it is not the best for managing or listing the issues for various sources. – jakapo May 9 '16 at 2:30

We use Jira to manage our agile process, which means we can create new stories or defects or enhancements, and we attached our usability findings to them.

This allows the team to assign severity and priority to what we raise. They can now be added to a particular sprint and can be assigned to a developer as a task.

I have done the same thing using another tool called Rally in the past.

In both tools we created customized UX tags which help us to keep things organised.

Not the answer you're looking for? Browse other questions tagged or ask your own question.