XP: Extreme Programming & Product Usability

5 Dec 2003 - 2:12pm
844 reads
Michael Quibuyen

They don't fit in. :)

Here's why:

XP relies on a "customer" to decide which features should be implemented
and when. A "customer" may be a product/project manager, customer service
employee, a marketing resource, etc. or even a user.

The tragedy here is that this "customer" provides direct, face-to-face
input with the development team to determine which features must be
implemented and when.

As interaction designers and user-centered types, we know that users or XP
"customers" can't articulate what they want, so their direct input can
result in serious interaction problems (among other issues).

The XP methodology was crafted by developers, so this might explain why
this flaw exists, however I feel that it could be easily modified to
properly address the human factor in software.


> I'm interested in hearing from anyone here who has experience (good or
> bad) with the Scrum/XP (eXtreme Programming) process for software
> development and how Interaction Design, Human Factors and Usability fit
> in.
> Background info: http://www.xprogramming.com/what_is_xp.htm
> _______________________________________________
> Interaction Design Discussion List
> discuss at interactiondesigners.com
> --
> to change your options (unsubscribe or set digest):
> http://discuss.interactiondesigners.com --
> Questions: lists at interactiondesigners.com
> --
> Announcement Online List (discussion list members get announcements
> already) http://interactiondesigners.com/announceList/
> --
> http://interactiondesigners.com/

Syndicate content Get the feed