The XP Customer Team: A Grounded Theory

The initial definition of XP resulted in many people interpreting the on-site customer to be a single person. We have conducted extensive qualitative research studying XP teams, and one of our research questions was “who is the customer”? We found that, rather than a single person, a customer team always exists. In this paper we outline the different roles that were typically on the team, which range from the recognized “Acceptance Tester” role to the less recognized roles of “Political Advisor” and “Super-Secretary”.

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

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

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

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

[5]  T. Kahkonen,et al.  Agile methods for large organizations - building communities of practice , 2004, Agile Development Conference.

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

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

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

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

[10]  Angela Martin.  The Role of Customers in Extreme Programming Projects , 2009 .

[11]  C. Brodsky.  The Discovery of Grounded Theory: Strategies for Qualitative Research , 1968 .

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

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

[14]  Tuomo Kähkönen,et al.  Agile Methods for Large Organizations - Building Communities of Practice , 2004, Agile Development Conference.

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

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

[17]  Ken Schwaber,et al.  AGILE DEVELOPMENT CONFERENCE ADC 2003 , 2003 .

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

[19]  Lawrence D. Pohlmann,et al.  Requirements By Collaboration , 2003 .

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

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

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