Advertisement

Customers and Userscustomeruser

  • Orit Hazzan
  • Yael Dubinsky
Chapter
Part of the Undergraduate Topics in Computer Science book series (UTICS)

Abstract

Customers have a key role is agile software development processes. The Agile Manifesto Agile Manifesto statement “customer collaborationcustomer over contract negotiation” explicitly suggests alternative work relationships with the customer, in which the customer is part of the team, rather than an entity with whom team members and management argue about what should be developed and when, and what should not be developed at all. This chapter describes the customer role in agile development environments and how to enhance communication with the customer. In many cases, the customer also represents the user group and is expected to evaluate the software product from the user perspective. This, however, turns out to be an ineffective mechanism in many cases. Accordingly, this chapter also describes the users’ role and presents a mechanism to increase their involvement and feedback during the development process. Specifically, data obtained from user evaluations is used to refine the user interface design, to increase product usability, and, consequently, to increase product quality.

Keywords

User Evaluation Software Project User Centered Design Short Sequence Repetition Agile Development 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

References

  1. Beck KBeck K (2000) Extreme programming explained: embrace change. Addison-Wesley, Reading, MAGoogle Scholar
  2. Beck K,Beck K Fowler MFowler M (2000) Planning extreme programming. Addison-Wesley, Reading, MAGoogle Scholar
  3. Blomkvist SBlomkvist S (2005) Towards a model for bridging agile development and user-centered design. In: Seffah A, Gulliksen J, Desmarais M (eds) Human-centered software engineering—integrating usability in the development process. Springer, Dordrecht, The NetherlandsGoogle Scholar
  4. Dix A,Dix A Finlay JFinlay J, Abowd GDAbowd GD, Beale RBeale R (2004) Human-computer-interaction, 3rd ed. Scotprint, HaddingtonGoogle Scholar
  5. Dubinsky Y, Hazzan O, Keren AKeren A (2005a) introducing extreme programming into a software project at the israeli air force. Proceedings of the 6th international conference on extreme programming and agile processes in software engineering. Sheffield University, UKGoogle Scholar
  6. Dubinsky Y, Talby DTalby D, Hazzan O, Keren AKeren A (2005b) Agile metrics at the Israeli air force. Agile conference, Denver, COGoogle Scholar
  7. Dubinsky Y, Catarci TCatarci T, Kimani SKimani S (2007) A user-based method for speech interface development. In: Stephanidis C (ed) Universal access in HCI, part I, HCII, LNCS 4554, HCI international, Beijing, China. pp 355–364Google Scholar
  8. Gittins R,Gittins R Hope SHope S (2001) A study of human solutions in extreme programming. 13th annual workshop of the psychology of programming interest group. pp 41–51Google Scholar
  9. Hazzan O, Dubinsky Y (2003) Bridging cognitive and social chasms in software development using extreme programming. Proceedings of the 4th international conference on extreme programming and agile processes in software engineering, Genoa, Italy. pp 47–53Google Scholar
  10. Hwong B,Hwong B Laurance DLaurance D, Rudorfer ARudorfer A, Song XSong X (2004) User-centered design and agile software development processes. Identifying 2004, workshop bridging gaps between HCI and software engineering and design, and boundary objects to bridge them. CHI workshop, Vienna, AustriaGoogle Scholar
  11. ISO 9241–11ISO 9241-11 (1998) Ergonomic requirements for office work with visual display terminals: guidance on usabilityGoogle Scholar
  12. Johnson DH,Johnson DH Caristi JCaristi J (2001) Extreme programming and the software design course. XP/Agile Universe websiteGoogle Scholar
  13. Lakoff G,Lakoff G Johnson MJohnson M (1980) Metaphors we live by. University of Chicago PressGoogle Scholar
  14. Lawler JMLawler JM (1999) Metaphors we compute by. In: Hickey DJ Figures of thought: for college writers. Mayfield PublishingGoogle Scholar
  15. McInerney P,McInerney P Maurer FMaurer F (2005) UCD in agile projects: dream team or odd couple? Interactions 12(6):19–23CrossRefGoogle Scholar
  16. Mullet DMullet D (1999) The software crisis. Benchmarks Online—a monthly publication of Academic Computing Services 2(7): http://www.unt.edu/benchmarks/archives/1999/july99/crisis.htm
  17. Nielsen J,Nielsen J Landauer TKLandauer TK (1993) A mathematical model of the finding of usability problems. Proceedings of ACM INTERCHI’93 conference, Amsterdam, The Netherlands, pp 206–213Google Scholar
  18. Norman DNorman D (2006) Why doing user observations first is wrong. ACM Interact July-August 50ffGoogle Scholar
  19. Rogers Y,Rogers Y Preece JPreece J, Sharp HSharp H (2002) Interaction design: beyond human-computer interaction. Wiley, New YorkGoogle Scholar
  20. Standish Group Chaos ReportChaos Report Standish Group: http://www.standishgroup.com/sample_research/ chaos_1994_2.php
  21. Vredenburg K,Vredenburg K Isensee SIsensee S, Righi CRighi C (2002) User-centered design: an integrated approach. Software Quality Institute Series, Prentice Hall PTRGoogle Scholar
  22. Wilson DWilson D (2001) Teaching XP: a case study. XP/Agile Universe websiteGoogle Scholar

Copyright information

© Springer-Verlag London 2008

Authors and Affiliations

  • Orit Hazzan
    • 1
  • Yael Dubinsky
    • 2
  1. 1.Department of Education in Technology and Science TechnionIsrael Institute of TechnologyHaifaIsrael
  2. 2.Department of Computer Science TechnionIsrael Institute of TechnologyHaifaIsrael

Personalised recommendations