Upfront design and agile don’t mix well
It’s an interesting problem to try and mix traditional design tasks – visual polish, user research testing, etc. – to an agile development process. A weekly development cycle doesn’t leave much room for several iterations of mockups, the immense effort of recruiting and interviewing users, and all these other important tasks.
Anyway, I was sent this recent link I’d encourage you to read on 12 emerging best practices for adding UX work to Agile development.
Here are the list of 12:
- Drive: UX practitioners are part of the customer or product owner team
- Research, model, and design up front – but only just enough
- Chunk your design work
- Use parallel track development to work ahead, and follow behind
- Buy design time with complex engineering stories
- Cultivate a user validation group for use for continuous user validation
- Schedule continuous user research in a separate track from development
- Leverage user time for multiple activities
- Use RITE to iterate UI before development
- Prototype in low fidelity
- Treat prototype as specification
- Become a design facilitator
In general, the best practices are about taking the down the level of fidelity in the design process and trying to work ahead of the engineers so that they get the fast feedback they need. Definitely worth reading.PS. Get new updates/analysis on tech and startups
I write a high-quality, weekly newsletter covering what's happening in Silicon Valley, focused on startups, marketing, and mobile.