“UX and Development cannot exist in the same Agile workstream” might sound like an outlandish claim but if you fully understand, it’s obvious. Forcing things to work as with the picture above is not a good idea.
Can UX be Agile yes, of course in so far that all the effort and artefacts required to deliver UX can exist in an Agile UX workstream.
UX includes user research, user requirement, KPI’s, system-wide taskflows, concepts, concept testing, persona definition, user roles, user journeys, usability and accessibility standards, sitemaps, key pathway wireframes.
Development can also be Agile, but not all of it, infrastructure and front end need to be in separate workstreams.
The simple way to express this is to talk through backlog items in a greenfield system;
The user can login…..
- UX will take days
- Front end will take weeks
- Back end will take months
The problem is not size it’s Trajectory and Dependencies;
- UX = T small, understood activity : D access to target audience to validate success and failure paths
- Fe = T mid, may need investigation : D access to dummy credentials store
- Be = T long, will require architecture to respond to scalability and bandwidth changes : D modelling data, server set up, pen testing
Once there is a fuller understanding of these very different aspects of defining, designing, building and deploying it’s become clear that these areas have common points but cannot be run together as and Agile project and to tell client’s that they are is not true.
Agilists don’t call this blind behaviour Agile, we call it Fragile (When Agile becomes Fragile nobody Wins) as we know it will shatter at the first problem.
I remember being in the discussion at a state owned investment bank when the discussion was being had about which front-end language should be used on their new system interfaces and they choose Silverlight.
This choice was known with the full knowledge that Microsoft was going to drop it as it was not in their new architecture.
We discussed HTML5 but Silverlight was chosen, over objections.
So now 3 years on I still see them recruiting Silverlight people.
I have to ask at what point before Microsoft stops supporting Silverlight in 2021 will someone work out that they need to stop building new interfaces and go back and change out the existing ones.
Who is in charge of the technology risk side of the business??
It’s just the most embarrassing thing to hear intelligent people say UI/UX. It makes professional people cringe because your left wondering should you care that they are exposing ignorance or just let them get on with sounding like an idiot. I mean their ignorance is not your responsibility after all, or is it?
So what’s so bad? Well not knowing that UI is a tiny subset of UX should not be that bad?
It’s the total lack of knowledge that irks, I think. I mean when you first went to school there was always some kid who thought it was funny to pee in the middle of the class room. You look at those who can’t tell this difference between UI/UX in the same way. It’s very funny for kids, but you are wondering why they persist in peeing themselves in public. It’s almost as if its now their party trick and they are scared they won’t get attention otherwise.
Maybe in this respect ignorance is bliss but for everyone else they seem like a slightly odd child.