Jeff Patton
ABSTRACT
Extreme Programming appears to be a solution for discovering and meeting requirements faster (through close customer collaboration) as well as creating quality software. In practice we found XP did deliver high quality software quickly, but the resulting product still failed to delight the customer. Although the finished product should have been an exact fit, the actual end-user still ended up slogging through the system to accomplish necessary day-to-day work. This paper describes using interaction design in an agile development process to resolve this issue. Using interaction design as a day-to-day practice throughout an iterative development process helps our team at Tomax Technologies deliver high quality software, while feeling confident the resulting software will more likely meet end-user expectations. The method of Interaction Design followed here is based on Constantine and Lockwood's Usage-Centered Design. Recommendations are provided on how to practice an agile form of U-CD and how to incorporate bits of Interaction Design thinking into every day development and product planning decisions.
- Agile Alliance http://www.agilealliance.com]]Google Scholar
- Beck, K., Cunningham, R., A Laboratory For Teaching Object Oriented Thinking, (1989) http://c2.com/doc/oopsla89/paper.html]] Google ScholarDigital Library
- Beck, K., Extreme Programming Explained, Adison-Wesley (1999)]] Google ScholarDigital Library
- Cockburn, A., Writing Effective Use Cases, Addison-Wesley (2000)]] Google ScholarDigital Library
- Cockburn, A., Agile Software Development, Addison-Wesley (2001)]] Google ScholarDigital Library
- Constantine L. & Lockwood L., Software For Use, Adison-Wesley, (April 1999)]]Google Scholar
- Constantine, L., Windl, H., Noble, J., & Lockwood, L. From Abstract to Realization in User Interface Designs: Abstract Prototypes Based on Canonical Abstract Components (2000) http://www.foruse.com/Files/Papers/canonical.pdf]]Google Scholar
- Constantine L., Process Agility and Software Usability (2001) http://www.foruse.com/Files/Papers/agiledesign.pdf]]Google Scholar
- Cooper, A., About Face, Hungry Minds Inc. (1995)]]Google Scholar
- Cooper, A., The Inmates are Running the Asylum, Sams (1999)]] Google ScholarDigital Library
- Fowler, M., Refactoring: Improving the Design of Existing Code, Addison-Wesley (1999)]] Google ScholarDigital Library
- Jeffries, R., Anderson, A., Hendrickson, C., Extreme Programming Installed, Addison-Wesley (2000)]] Google ScholarDigital Library
- Mathaissen]]Google Scholar
- Nelson, E., Extreme Programming vs. Interaction Design (2002) http://www.fawcette.com/interviews/beck_cooper/]]Google Scholar
- Schwaber, K., Beedle M., Agile Software Development with Scrum, Prentice Hall, (2001)]] Google ScholarDigital Library
- Test Driven Programming http://xp.c2.com/TestDrivenProgramming.html]]Google Scholar
- Wirfs-Brock, ⟨Which paper did she first document conversational use cases? Find this.⟩]]Google Scholar
- Extreme Programming Yahoo Group http://groups.yahoo.com/group/extremeprogramming/]]Google Scholar
Index Terms
- Hitting the target: adding interaction design to agile software development
Recommendations
Empirical Study of Agile Software Development Methodologies: A Comparative Analysis
In today's software industry, technological prowess and ever-evolving customer requirements have led to more complex software demands. Agile based software development is increasingly being adopted by the software practitioners as it assures early ...
An initial investigation of test driven development in industry
SAC '03: Proceedings of the 2003 ACM symposium on Applied computingTest Driven Development (TDD) is a software development practice in which unit test cases are incrementally written prior to code implementation. In our research, we ran a set of structured experiments with 24 professional pair programmers. One group ...
Field Experiences with eXtreme Programming: Developing an Emergency Response System
<P> eXtreme Programming (XP) is a well-known agile software development method. While a number of reports have been published on explaining the XP methodology and the perceived benefits when using XP for system development in recent years, less is known ...
Reviews
Satadip Dutta
Interaction design holds a very important place in the software development process. The star life cycle [1] was one of the first software development methodologies that tried to integrate interaction design into software development. This paper takes an important step in merging the benefits of interaction design with agile software development. The paper presents a case study that describes the problems faced by the development team in prioritizing features that would significantly benefit the user. Identifying the right feature set allows developers to set development priorities, and supports the matching of customer expectations. The author describes the process of adding interaction design to the extreme programming methodology. The highlight of the paper appears in two very aptly named sections: "What Worked" and "What was Bumpy." The author then proceeds to provide a set of guidelines derived from this experience. The author has a delightful writing style that deviates from traditional and formal prose. The value of the work is derived from a very hands-on approach to practicing the techniques described. The paper provides an insightful look at the techniques described that will help projects by enabling them to build on the author's experience and knowledge. This paper will be extremely useful for software development projects that aim to integrate interaction design along with principles of extreme programming. Online Computing Reviews Service
Access critical reviews of Computing literature here
Become a reviewer for Computing Reviews.
Comments