{"id":433,"date":"2006-12-14T00:06:14","date_gmt":"2006-12-14T05:06:14","guid":{"rendered":"http:\/\/josh.ev9.org\/weblog\/archives\/433"},"modified":"2006-12-14T00:07:02","modified_gmt":"2006-12-14T05:07:02","slug":"agile-user-centered-design","status":"publish","type":"post","link":"http:\/\/josh.ev9.org\/weblog\/archives\/433","title":{"rendered":"Agile + User Centered Design"},"content":{"rendered":"

So, Marc<\/a> says User Centered Design is compatible with Agile<\/a>. I think I agree, but with a caveat or two.<\/p>\n

They’ve Got Different Foci<\/strong><\/p>\n

The User Centered Design<\/a> methodology is based on one simple concept: the person who will eventually use the system should be the focus of the design process. There are many processes, techniques, and tricks<\/a> that flow from this principle, but they all take the user as the core element to be studied in order to come to a design specification. In my studies, I haven’t come across any examples of a UCD process specifying exactly how<\/em> the tool should be built, rather, the design process specifies tool that is to be built.
\nIn contrast, Agile methods guide the development of a tool that is being actively specified. XP and its brethren guide a development process, not a design<\/a> process. Design plus development are made to be together. It has been this way since the beginning of industrial design<\/a>, architecture<\/a>, and other older, more standardized design fields.<\/p>\n

Agile is what you make it<\/strong><\/p>\n

As much as many Agile backers may think otherwise, I believe there is no standardized Design<\/a> practice within Agile practices. Sure we create UI prototypes. Sure we work with the Customer to make sure they’re getting what they want, which seems somewhat similar to Participatory Design<\/a> practices started in the 1970s. But there isn’t much of a true Design<\/a> practice in most Agile projects, at least the ones that I’ve read about and seen on the job.<\/p>\n

I’m not yet ready to give up hope, though. Remember back from the thesis of this entry, I agree with Marc’s sentiments.<\/em> Agile methods that I’ve seen in practice have been so extensible and open to change (I guess that’s sort of the definition of agile) that I see no reason that UCD and general Design practices can be built into Agile frameworks. In fact, I think we’re pioneering some of these practices at ThoughtWorks<\/a> every day.<\/p>\n

With a little work, and some tweaks in the design and development process, I think we can make it easy to marry the dependable, successful development brought about by Agile methods with the UCD processes that regularly create excellent, user (and customer) accepted software tools. We’re not there yet, but each day we’re getting a little closer, at least within the walls of TW.<\/p>\n","protected":false},"excerpt":{"rendered":"

So, Marc says User Centered Design is compatible with Agile. I think I agree, but with a caveat or two. They’ve Got Different Foci The User Centered Design methodology is based on one simple concept: the person who will eventually use the system should be the focus of the design process. There are many processes, […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"nf_dc_page":"","_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[16,17,2,21,12,13],"tags":[],"class_list":["post-433","post","type-post","status-publish","format-standard","hentry","category-agile-development","category-design","category-hci-topic","category-professional","category-technology","category-thoughtworks"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t