Comments on: Agile UXD http://www.pathf.com/blogs/2007/05/agile_uxd/ Running commentary about agile development, user experience design and Ajax. Fri, 05 Dec 2008 10:10:03 +0000 http://wordpress.org/?v=2.5.1 By: Alice Toth http://www.pathf.com/blogs/2007/05/agile_uxd/#comment-822 Alice Toth Fri, 08 Jun 2007 04:15:08 +0000 http://www.pathf.com/blogs/2007/05/agile_uxd/#comment-822 <p>For me, one of the bigger challenges is having to design and develop before all of the business requirements are known. As you stated in your post, you don't really want to refactor the UI with each public release. </p> <p>So we need to create a UI that's flexible enough to accommodate change gracefully without necessarily knowing if the changes will be incremental or a 180. Naturally, this can be easier said than done. The key is having an entire team that's committed to having change (or iterations) as part of the process.</p> <p>The value with an agile UXD, however, outweighs any discomfort. We start getting user (including developer) feedback early in the development lifecycle where we can optimize the design or a workflow at less cost to the project. In the end, I believe we create a more usable product resulting in subsequent releases that can focus on features, not fixes.</p> For me, one of the bigger challenges is having to design and develop before all of the business requirements are known. As you stated in your post, you don’t really want to refactor the UI with each public release.

So we need to create a UI that’s flexible enough to accommodate change gracefully without necessarily knowing if the changes will be incremental or a 180. Naturally, this can be easier said than done. The key is having an entire team that’s committed to having change (or iterations) as part of the process.

The value with an agile UXD, however, outweighs any discomfort. We start getting user (including developer) feedback early in the development lifecycle where we can optimize the design or a workflow at less cost to the project. In the end, I believe we create a more usable product resulting in subsequent releases that can focus on features, not fixes.

]]> By: Dave http://www.pathf.com/blogs/2007/05/agile_uxd/#comment-821 Dave Thu, 07 Jun 2007 22:23:41 +0000 http://www.pathf.com/blogs/2007/05/agile_uxd/#comment-821 <p>Thanks for an interesting post. What are the biggest challenges you've had so far in incorporating the Agile approach?</p> <p>I've written on this topic before here:<br /> <a href="http://www.infoq.com/articles/agile-useability-churchville" rel="nofollow">http://www.infoq.com/articles/agile-useability-churchville</a></p> <p>Always curious how other pracitioners are merging UX and Agile methods.</p> Thanks for an interesting post. What are the biggest challenges you’ve had so far in incorporating the Agile approach?

I’ve written on this topic before here:
http://www.infoq.com/articles/agile-useability-churchville

Always curious how other pracitioners are merging UX and Agile methods.

]]>