An Ideal Customer: A Grounded Theory of Requirements Elicitation, Communication and Acceptance on Agile Projects

This chapter explores the reality of the customer role – a critical, complex, and demanding role on agile teams. Despite initial difficulties, customers love agile development and would not do it any other way, but they also encountered many difficulties in their day-to-day work. In this chapter we describe the practices that have emerged to ensure the role works effectively and sustainably, and how the role has evolved from an individual to a team. We hope customers will find this chapter helpful in performing their role, and programmers will find it useful to understand the complexities of customer’s role on the project.

[1]  B. Glaser.  Theoretical Sensitivity: Advances in the Methodology of Grounded Theory , 1978 .

[2]  E. Whitley.  Golem, Inc.: A Comment on Certain Points Where Cybernetics Impinges on Religion , 1999 .

[3]  Brian Fitzgerald,et al.  Systems development methodologies: the problem of tenses , 2000, Inf. Technol. People.

[4]  Lisa Baker,et al.  Using Persona with XP at LANDesk Software, an Avocent Company , 2008, Agile 2008 Conference.

[5]  Nathan Brewer,et al.  Improving communication between customers and developers , 2005, Agile Development Conference (ADC'05).

[6]  David E. Avison,et al.  The fiction of methodological development: a field study of information systems development , 1999, Inf. Technol. People.

[7]  Mark Isham,et al.  Agile Architecture IS Possible You First Have to Believe! , 2008, Agile 2008 Conference.

[8]  John M. Hammer,et al.  Embracing Change: An XP Experience Report , 2003, XP.

[9]  Martin Fowler,et al.  Planning Extreme Programming , 2000 .

[10]  Joseph Bergin,et al.  Introducing agile development (XP) into a corporate Webmaster environment - an experience report , 2005, Agile Development Conference (ADC'05).

[11]  Tom DeMarco,et al.  Structured Analysis and System Specification , 1978 .

[12]  Ken Schwaber,et al.  Agile Software Development with SCRUM , 2001 .

[13]  David Hussman.  Coaching a Customer Team , 2003, XP.

[14]  A. Strauss,et al.  The discovery of grounded theory: strategies for qualitative research aldine de gruyter , 1968 .

[15]  James Noble,et al.  XP Customer Practices: A Grounded Theory , 2009, 2009 Agile Conference.

[16]  Lynn Miller.  Case study of customer input for a successful product , 2005, Agile Development Conference (ADC'05).

[17]  Kelly Weyrauch,et al.  What are we arguing about? A framework for defining agile in our organization , 2006, AGILE 2006 (AGILE'06).

[18]  Ellen Gottesdiener.  Requirements by Collaboration: Workshops for Defining Needs , 2002 .

[19]  Jonathan Clark,et al.  Something to believe in [Reed Elsevier] , 2006, AGILE 2006 (AGILE'06).

[20]  Kent L. Beck,et al.  Extreme programming explained - embrace change , 1990 .

[21]  Jonathan Rasmusson.  Agile project initiation techniques - the inception deck & boot camp , 2006, AGILE 2006 (AGILE'06).

[22]  Todd Wilkens,et al.  Subject to Change: Creating Great Products and Services for an Uncertain World , 2008 .

[23]  Paul Hodgetts.  Refactoring the development process: experiences with the incremental adoption of agile practices , 2004, Agile Development Conference.

[24]  James Noble,et al.  The XP Customer Team: A Grounded Theory , 2009, 2009 Agile Conference.

[25]  James A. Highsmith,et al.  Adaptive Software Development: A Collaborative Approach to Managing Complex Systems , 1999 .

[26]  Paul A. Beavers,et al.  Managing a Large "Agile" Software Engineering Organization , 2007, Agile 2007 (AGILE 2007).

[27]  Marcus Evans,et al.  Scaling Product Ownership , 2007, Agile 2007 (AGILE 2007).

[28]  Tim Mackinnon,et al.  XP-Call in the Social Workers , 2003, XP.

[29]  Karen Holtzblatt,et al.  An Agile Customer-Centered Method: Rapid Contextual Design , 2004, XP/Agile Universe.

[30]  Victor Weinberg,et al.  Structured Analysis , 1978 .

[31]  Mary Lynn Manns,et al.  Fearless Change: Patterns for Introducing New Ideas , 2004 .