I am trying integrate a UX team of about 14 UX designers into a software engineering organization of about 100 developers. One of many challenges I'm trying to figure out is how to deal with things like usability testing. I'm working off lots of assumptions here (please correct me if these are bad assumptions):
The UX team's work should be in the backlog as user stories. Point of clarification - right now, there is a design backlog and then there is an engineering backlog. So we're not "full stack."
A user story should be able to be completed in one sprint.
So here's my question:
Does it make any sense to write a user story for a usability test? It doesn't seem user focused. For example, "As a user I want the application to be usability tested so that we can identify problems and fix them." What? That's nonsense. How should we integrate these kinds of tasks into our backlog?
It usually takes 4+ weeks to complete a usability test. We have to recruit the participants (very narrow demographic), plan the test, run the test, and then report on the test. Can't get all that done in a 2 week sprint. What now? How do I write a story for something smaller than the full usability test? A story just for writing the test plan, then another story for recruiting the participants? That really seems to stretch the definition of a user story.