UX design for an “under-defined” project using Agile
Always interesting to see how UX designers (UI Analysts in my company) are adjusting to the Agile life.
ap3x:
Recently I’ve been working on a big complicated project that is hard to define. I’ve been starting to question my usual approach to designing for the user experience (UX).
I’ve come to the conclusion that when projects are hard to define, it might be best to keep the initial design phase to a minimum. Rather than developing a full design specification, HTML prototypes can be used to make sure everyone has a clear idea of what’s being built. These HTML prototypes can be gradually turned into functional prototypes in short bursts of Agile Software Development. The visual design during these short bursts is kept to a minimum - focus is on the organisation of the interface with function being much more dominant than form. When everyone’s agreed that we’re on track, the visual design phase becomes something more like a re-design.
Here’s my reasoning…
