Advertisement

Agile Undercover: When Customers Don’t Collaborate

  • Rashina Hoda
  • James Noble
  • Stuart Marshall
Part of the Lecture Notes in Business Information Processing book series (LNBIP, volume 48)

Abstract

Customer collaboration is vital to Agile projects. Through a Grounded Theory study of New Zealand and Indian Agile teams we discovered that lack of customer involvement was causing problems in gathering and clarifying requirements, loss of productivity, and business loss. “Agile Undercover” allows development teams to practice Agile despite insufficient or ineffective customer involvement. We present the causes and consequences of lack of customer involvement on Agile projects and describe the Agile Undercover strategies used to overcome them.

Keywords

Agile Software Development Customer Involvement Agile Undercover Grounded Theory 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Adolph, S., et al.: A Methodological Leg to Stand on. In: CASCON. ACM, USA (2008)Google Scholar
  2. 2.
    Beaumont, S.: The Definition of READY. Xebia blogs, http://blog.xebia.com/2009/06/19/the-definition-of-ready (December 4, 2009)
  3. 3.
    Beck, K.: Extreme Programming Explained, 2nd edn. Addison-Wesley, Reading (2004)Google Scholar
  4. 4.
    Boehm, B., Turner, R.: Rebalancing Your Organization’s Agility and Discipline. In: Marchesi, M., Succi, G. (eds.) XP 2003. LNCS, vol. 2675, Springer, Heidelberg (2003)Google Scholar
  5. 5.
    Chow, T., Cao, D.: A survey study of critical success factors in agile software projects. J. Syst. Softw., pp. 961–971 (2008)Google Scholar
  6. 6.
    Cockburn, A.: People and Methodologies in Software Development. PhD thesis, University of Oslo, Norway (2003)Google Scholar
  7. 7.
    Coleman, G., et al.: Using GT to Understand Software Process Improvement: A Study of Irish Software Product Companies. J. Inf. Softw. Technol. 49(6), 654–667 (2007)CrossRefGoogle Scholar
  8. 8.
    Dybå, T., Dingsoyr, T.: Empirical Studies of Agile Software Development: A Systematic Review. J. Inf. Softw. Technol. 50(9-10), 833–859 (2008)CrossRefGoogle Scholar
  9. 9.
    Fraser, S., et al.: The Role of the Customer in Software Development: the XP Customer - Fad or Fashion? In: OOPSLA, pp. 148–150. ACM, USA (2004)Google Scholar
  10. 10.
    Georgieva, S., Allan, G.: Best Practices in Project Management Through a Grounded Theory Lens. E. J. Business Research Methods (2008)Google Scholar
  11. 11.
    Glaser, B.: Basics of Grounded Theory Analysis: Emergence vs. Forcing, CA (1992)Google Scholar
  12. 12.
    Glaser, B.: Theoretical Sensitivity. Sociology Press, Mill Valley (1978)Google Scholar
  13. 13.
    Glaser, B.: The Grounded Theory Perspective III: Theoretical Coding. Sociology Press, Mill Valley (2005)Google Scholar
  14. 14.
    Glaser, B., Strauss, A.L.: The Discovery of Grounded Theory. Aldine, Chicago (1967)Google Scholar
  15. 15.
    Grisham, P.S., Perry, D.E.: Customer relationships and Extreme Programming. In: HSSE 2005. ACM, USA (2005)Google Scholar
  16. 16.
    Hanssen, G.K., Fgri, T.E.: Agile Customer Engagement: A Longitudinal Qualitative Case Study. In: ISESE, Brazil, pp. 164–173 (2006)Google Scholar
  17. 17.
    Highsmith, J., Fowler, M.: The Agile Manifesto. Software Development Magazine (2001)Google Scholar
  18. 18.
    Hoda, R., Noble, J., Marshall, S.: Negotiating Contracts for Agile Projects: A Practical Perspective. In: XP 2009, Italy (2009)Google Scholar
  19. 19.
    Hoda, R., Noble, J., Marshall, S.: Agile Undercover. In: Agile 2009 RiP, Chicago (2009)Google Scholar
  20. 20.
    Judy, K.H., Krumins-Beens, I.: Great Scrums Need Great Product Owners: Unbounded Collaboration and Collective Product Ownership. In: HICSS, Hawai, pp. 462–462 (2008)Google Scholar
  21. 21.
    Kan, M.M., Parry, K.W.: Identifying Paradox: A grounded theory of leadership in overcoming resistance to change. The Leadership Quaterly, 467–491 (2004)Google Scholar
  22. 22.
    Korkala, M., Abrahamsson, P., Kyllonen, P.: A Case Study on the Impact of Customer Communication on Defects in Agile Software Development. In: AGILE 2006, USA (2006)Google Scholar
  23. 23.
    Lowery, M., Evans, M.: Scaling Product Ownership. In: Agile 2007, USA (2007)Google Scholar
  24. 24.
    Mann, C., Maurer, F.: A Case Study on the Impact of Scrum on Overtime and Customer Satisfaction. In: ADC, pp. 70–79. IEEE Computer Society, USA (2005)Google Scholar
  25. 25.
    Martin, A., et al.: The XP customer role in practice: Three studies. In: ADC 2004, pp. 42–54. IEEE Computer Society, Washington (2004)Google Scholar
  26. 26.
    Misra, S.C., et al.: Identifying some important success factors in adopting agile software development practices. J. Syst. Softw. 82(11), 1869–1890 (2009)CrossRefGoogle Scholar
  27. 27.
    Nerur, S., et al.: Challenges of migrating to agile methodologies. Com. ACM, 72–78 (2005)Google Scholar
  28. 28.
    Pikkarainen, M., et al.: The impact of agile practices on communication in software development. J. Empirical Softw. Engg., 303–337 (2008)Google Scholar
  29. 29.
    Schwaber, K., Beedle, M.: Agile Software Development with Scrum. Prentice-Hall, Englewood Cliffs (2001)Google Scholar
  30. 30.
    Strauss, A., Corbin, J.: Basics of Qualitative Research. Sage, Newbury Park (1990)Google Scholar
  31. 31.
    Whitworth, E., Biddle, R.: The Social Nature of Agile Teams. In: Agile 2007, pp. 26–36. IEEE Computer Society, USA (2007)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2010

Authors and Affiliations

  • Rashina Hoda
    • 1
  • James Noble
    • 1
  • Stuart Marshall
    • 1
  1. 1.Victoria University of WellingtonNew Zealand

Personalised recommendations