UX Design with Scrum
Hi everyone,
I'm currently working on an essai about Agile UX Design for a Master2 at GOBELINS, L'école de l'image in Paris, France. As a UX Designer, I've joined a team working well with Scrum.
I do feel that being a UX designer in a Scrum team is not easy, because some time
user research takes more than a sprint to be done.
On the other hand, developers often "wait for me" so I can deliver new screens to implement
them... and so I feel I'm on a waterfalls process falback.
I read blogs and posts about "how to do UX agile design". Some people recommend to "do design spikes" or to "be 2 sprints ahead", some even imagine a "Design owner" role...
I'm now interviewing people working with Scrum about this, and I'd be happy to have your feedback...
Karine
Hello Karine,
I use to work on this question with the product owner. From my experience (a short one) I'd recommend to be 2 sprints ahead, this way you can have the customers express their feedback so that you have one sprint to adapt your UX before the developers can start implementing the underlying feature.
According to my understanding of Scrum, an item should start and end in the same sprint. How does the UX design fits in this affirmation, if this quote is true?
because some time user research takes more than a sprint to be done.
Choisel.
According to my understanding of Scrum, an item should start and end in the same sprint. How does the UX design fits in this affirmation, if this quote is true?
because some time user research takes more than a sprint to be done.
Hi Choisel,
thanks for your feedback.
You're pointing exactling what I'm wondering: I entended to get customers feedback during my first sprint, but I never get a chance to do it: the product I'm working on is a B to B one, has only a few customers I could ask feedback, and I have "the big pictures" only now... 3 sprints later I started working (also I'm alone doing it so I may need more time than a UX team working together).
I was thinking that maybe there's a part of their work that could fit well with Scrum (once you have had the time to figure out what your customers need and how things work for them) ; but another that needs to be done before being able to create user stories... (and so am I back to a waterfall conception?)
That's that particular point I'd like to have feedback for. I'm interested in how other teams work, regarding their size maybe? their projects? uses to work together? their product owner?... and whatever parameter could change things.
Karine