UX design in Agile projects

By: on January 15, 2014

We’ve been making a habit of collaboration with partners for what seems like forever, so why is it that we find it hard to get the formula right with front-end designers? Are we a particularly fussy bunch, orĀ is there something more systematic going on?

Recently we’ve been working with the Agile Research Network who were interested in researching this area and its been useful to have someone external observing projects and documenting conclusions.

The Agile mantra of avoiding BDUF (Big Design Up Front), fails to provide specific guidance over what constitutes “Enough DUF” and guidelines are helpful. Some of what was highlighted was obvious, some less so, here’s a sample:

  • Design prototypes, or demonstrators that look too perfect are dangerous
  • Pixel-perfect UX designs will increase resistance to change
  • Prioritisation and de-scoping renders pixel-perfect designs unnecessary
  • Good UX, like good technical design should be modular
  • Some issues with the design will only be found once you start implementing
  • Get UX and technical designers collaborating on each others’ decisions
  • Consider using an analyst to work closely with both teams documenting requirements conclusions from their work

An initial white paper from the ARN was presented at the Agile Conference in October 2013, a more in depth research paper is under preparation as the moment.





Comments are closed