In a recent series of consulting projects, I served as the designer for a software development team working with agile development methods, widely known through the most severe of these methods, Extreme Programming, or XP. The most salient aspect of the agile methods movement  and of XP is emphasis on rapid, iterative releases of working products at the expense of sophisticated planning and design. This seemingly anti-design approach is anathema to most designers, whose very existence depends on representing what is to be built. Although my experience was frustrating at times, I tried to keep an open mind…
You must be a member of SIGCHI, a subscriber to ACMís Digital Library, or an interactions subscriber to read the full text of this article.LOG IN TO READ THE FULL ARTICLE
GET ACCESSJoin ACM SIGCHI
In addition to all of the professional benefits of being a SIGCHI member, members get full access to interactionsí online content and receive the print version of the magazine bimonthly.
Subscribe to the ACM Digital Library
Get access to all interactions content online and the entire archive of ACM publications dating back to 1954. (Please check with your institution to see if it already has a subscription.)
Subscribe to interactions
Get full access to interactionsí online content and receive the print version of the magazine bimonthly.