I had a conversation with a colleague yesterday about Agile development environments and how it is difficult to evangelize usability and design with UX in mind. While I argued that it was completely possible to keep usability as a priority while still scrumming constantly and pushing the envelope of development, I realize that in larger organizations that may not have project managers who are UX focused, that the module aspect of agile development can really play havoc with the overall usability of the website/application of product.
The basics are:
- UX practitioners members are part of the Product ownership team
- Prioritize users for persona, modeling and research
- Chunking the design work, or user tasks
- Use parallel track development, moving back and forth in design work
- Get more design time for difficult design sections of the project with easy IX work out of the way first
- Keep a large group of validation users available
- Schedule continuous user research in a separate track from development
- Utilize user testing for multiple purposes (similar to #4)
- use RITE to iteratively test UI before development
- Prototype in low fidelity (consumables vs deliverables)
- Treat the prototype as the documentation/specifications
- As a UX practitioner, you should become a design facilitator, gathering ideas and deciding how to chunk them out
The details about each of these ‘best practices’ can be found in Jeff Patton’s article and I recommend reading it if you are a UX professional working in an Agile development environment.
An additional quote from the article I found sobering was:
Two secrets to success in software development are:
- Start sooner
- Build less software
There may be shortcuts in using the Agile system, but nothing can replace good usability research and focusing your team on one product at a time.