Fitting the User Experience Practice in an Agile Project Cycle
Last Thursday, Organic hosted a panel discussion on how to fit the User Experience practice into an Agile project cycle. For more information on what Agile is, see the Agile Manifesto or check out the Wikipedia entry.
So, Why is This an Interesting Topic for User Experience Professionals?
With a trend to quick iterations it's hard for us to figure out where our discipline fits in. As is the nature of agile, the UX design can change and it becomes difficult to maintain a consistent experience. Add to this an ill-defined agile process (many want to say they're "agile", but in reality they're not), a UXer might feel a loss of control. So, what's the solution?
Advice From the Panel
The biggest takeaway for our team of Experience Architects was not to compromise user testing. Test early and test often. It's a great way to learn if the designs are usable, especially if you have a hunch that there are issues. Don't have a huge budget for testing? No problem ... there are some "guerilla" testing methods that can get you the information you need (see below). Some testing is better than no testing.
Another great piece of advice: your analytics department is your best friend. Chances are, they've analyzed something similar and can provide valuable metrics to support your hypotheses. Seek them out and ask for their help.
Other Takeaways:
• If your budgets don't allow for extensive research then find guerilla methods for testing. Round up users in your company or take advantage of services such as fivesecondtest.com.
• Agile should be ... well ... agile. While there is technically a right and a wrong way to do agile, the process in itself should be adaptable. If it's not working for you, then use the elements that do make sense ... resolve to have more face to face interactions and stand up meetings. Whatever works for your environment.
• In the spirit of the adaptable process, consider getting a head start on the typical agile development cycle. When incorporating User Experience into Agile, begin with Iteration 0 where the User Experience people lay out some design patterns and architecture. Turn this over to development and stay a week or so ahead. For more information, see Lynn Miller's case study.
Anthony Viviano




