Skip to main content

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

  • Chapter
  • First Online:
Book cover Agile Software Development

Abstract

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.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
USD 54.99
Price excludes VAT (USA)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  • Beavers, P. A. (2007). Managing a Large "Agile" Software Engineering Organization. Agile 2007, Washington D.C, United States, IEEE Computer Society.

    Google Scholar 

  • Beck, K. (2000). eXtreme Programming Explained: Embrace Change, Addison-Wesley.

    Google Scholar 

  • Beck, K. (2004). eXtreme Programming Explained: Embrace Change. Second Edition., Addison-Wesley.

    Google Scholar 

  • Beck, K., M. Beedle, et al. (2001). "Manifesto for Agile Software Development". from http://agilemanifesto.org/.

  • Beck, K. and M. Fowler (2001). Planning Extreme Programming, Addison-Wesley.

    Google Scholar 

  • Beyer, H., K. Holtzblatt, et al. (2004). An Agile Customer-Centered Method: Rapid Contextual Design. XP Agile Universe, Calgary, Alberta, Canada.

    Google Scholar 

  • Broschinsky, D. and L. Baker (2008). Using Persona with XP at LANDesk Software, an Avocent Company. Agile 2008, Toronto, Canada, IEEE Computer Society.

    Google Scholar 

  • DeMarco, T. (1979). Structured Analysis and System Specification, Prentice-Hall.

    Google Scholar 

  • Fitzgerald, B. (2000). "Systems Development Methodologies: The Problem of Tenses". Information Technology and People 13(3): 174 - 185.

    Article  Google Scholar 

  • Fuqua, A. M. and J. M. Hammer (2003). Embracing Change: An XP Experience Report. Fourth Internal Conference on Extreme Programming and Agile Processes in Software Engineering, Genoa, Italy, Springer-Verlag.

    Google Scholar 

  • Ganis, M., D. Leip, et al. (2005). Introducing Agile Development (XP) into a Corporate Webmaster Environment - An Experience Report. Agile 2005, Denver, Colorado, United States, IEEE Computer Society.

    Google Scholar 

  • Glaser, B. G. (1978). Theoretical Sensitivity: Advances in the Methodology of Grounded Theory., The Sociology Press.

    Google Scholar 

  • Glaser, B. G. and A. L. Strauss (1967). The Discovery of Grounded Theory: Strategies for Qualitative Research. Chicago: Aldine.

    Google Scholar 

  • Gottesdiener, E. (2002). Requirements by Collaboration: Workshops for Defining Needs, Addison-Wesley.

    Google Scholar 

  • Highsmith, J. (2000). Adaptive Software Development: A Collaborative Approach to Managing Complex Systems., Dorset House Publishing.

    Google Scholar 

  • Hodgetts, P. (2004). Refactoring the Development Process: Experiences with the Incremental Adoption of Agile Processes. Agile Development Conference, Salt Lake City, Utah, United States, IEEE Computer Society.

    Google Scholar 

  • Honious, J. and J. Clark (2006). Something to Believe In. Agile 2006, Minneapolis, United States, IEEE Computer Society.

    Google Scholar 

  • Hussman, D. (2003). Coaching a Customer Team. Fourth Internal Conference on Extreme Programming and Agile Processes in Software Engineering, Genoa, Italy, Springer- Verlag.

    Google Scholar 

  • Isham, M. (2008). Agile Architecture is Possible - You First Have to Believe. Agile 2008, Toronto, Canada, IEEE Computer Society.

    Google Scholar 

  • Kahkonen, T. (2004). Agile Methods for Large Organisations - Building Communities of Practice. Agile Development Conference, Salt Lake City, Utah, United States, IEEE Computer Society.

    Google Scholar 

  • Lowery, M. and M. Evans (2007). Scaling Product Ownership. Agile 2007, Washington D.C, United States, IEEE Computer Society.

    Google Scholar 

  • Mackinnon, T. (2003). XP - Call in the Social Workers. Fourth International Conference on eXtreme Programming and Agile Processes in Software Engineering., Genoa, Italy, Springer-Verlag.

    Google Scholar 

  • Manns, M. L. and L. Rising (2004). Fearless Change: Patterns for Introducing New Ideas, Addison-Wesley.

    Google Scholar 

  • Martin, A. (2009). Exploring the Role of Customers in Extreme Programming Projects. PhD Thesis. New Zealand. http://researcharchive.vuw.ac.nz/handle/10063/877, Victoria University of Wellington. PhD: 150.

  • Martin, A., R. Biddle, et al. (2009). The XP Customer Team: A Grounded Theory. Agile 2009, Chicago, IEEE Computer Society.

    Google Scholar 

  • Martin, A., R. Biddle, et al. (2009). XP Customer Practices: A Grounded Theory. Agile 2009, Chicago, IEEE Computer Society.

    Google Scholar 

  • Merholz, P., T. Wilkens, et al. (2008). Subject To Change: Creating Great Products and Services for an Uncertain World, O'Reilly.

    Google Scholar 

  • Miller, L. (2005). Case Study of Customer Input for a Sucessful Product. Agile 2005, Denver, Colorado, United States, IEEE Computer Society.

    Google Scholar 

  • Nandhakumar, J. and D. E. Avison (1999). "The Fiction of Methodological Development: A Field Study of Information Systems Development". Information Technology and People 12(2): 1 - 28.

    Google Scholar 

  • Rasmusson, J. (2006). Agile Project Initiation Techniques - The Inception Deck and Boot Camp. Agile 2006, Minneapolis, United States, IEEE Computer Society.

    Google Scholar 

  • ResearchWare (2006). HyperResearch Qualitative Analysis Tool.

    Google Scholar 

  • Schwaber, K. and M. Beedle (2001). Agile Software Development with Scrum, Prentice- Hall.

    Google Scholar 

  • Takats, A. and N. Brewer (2005). Improving Communication between Customers and Developers. Agile 2005, Denver, Colorado, United States, IEEE Computer Society.

    Google Scholar 

  • Weyrauch, K. (2006). What Are We Arguing About? A Framework for Defining Agile in our Organization. Agile 2006, Minneapolis, United States, IEEE Computer Society.

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Angela Martin .

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2010 Springer-Verlag Berlin Heidelberg

About this chapter

Cite this chapter

Martin, A., Biddle, R., Noble, J. (2010). An Ideal Customer: A Grounded Theory of Requirements Elicitation, Communication and Acceptance on Agile Projects. In: Dingsøyr, T., Dybå, T., Moe, N. (eds) Agile Software Development. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-12575-1_6

Download citation

  • DOI: https://doi.org/10.1007/978-3-642-12575-1_6

  • Published:

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-642-12574-4

  • Online ISBN: 978-3-642-12575-1

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics