We can’t talk about the design, our UXer is not here today
What do you do when you are presenting a UX topic at an Agile conference to a majority non-UX audience, and you know they’ll be spending at least part of their break standing in a line waiting to order coffee? You run a survey of course!
During Agile Australia 2014, I took the opportunity to ask the conference attendees a bunch of questions around UX (via a survey at the coffee cart lines). One of the questions was:
“I see UXers as the owners of the design in a project. (i.e. if they are not there, the design should not be changed)”.
The result from this question was interesting. During my presentation, I’ll cover the results from the survey. I’ll then deep dive into the theme of design ownership and its impact on the productivity of an agile project team. I want to pose some questions to you – the audience and then discuss my thoughts on many misunderstandings of UX and how we UXers fit in an Agile team.
I’ll use some example Agile project case studies to show where things can go right or wrong when availability of individuals with dedicated ‘prescribed’ roles change.
UX is not wizardry – it’s a process, right?! So how does this mentality change what a teams does to deliver Agile projects. I’ll propose some thoughts on how we could mitigate risks associated with role changes to ensure a project can still run smoothly.
