Abstract
This chapter analyses the results of a series of observational studies of agile software development teams, identifying commonalities in collaboration, co-ordination and communication activities. Pairing and customer collaboration are focussed on to illustrate the nature of collaboration and communication, as are two simple physical artefacts that emerged through analysis as being an information-rich focal point for the co-ordination of collaboration and communication activities. The analysis shows that pairing has common characteristics across all teams, while customer collaboration differs between the teams depending on the application and organisational context of development.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Similar content being viewed by others
Notes
- 1.
Time-boxed units of development lasting 1–4 weeks are called “iteration’s” in XP; time-boxed units of development around four weeks are called “sprints” in Scrum.
- 2.
cf. Edwin Hutchins’ Cognition in the Wild, MIT Press, Cambridge, MA, 1995.
- 3.
Transitioning to XP is a process that can take place over a weekend or can require several months, depending on a range of factors such as team size, organizational culture and team member attitude, for example.
- 4.
We have observed pairings of a developer with a graphic designer, and a developer with a business analyst.
- 5.
Such italicized, bracketed material, in quotes, is an illustrative extract from our field notes.
- 6.
Software is released after a series of iterations, typically every few months. There is a layer of release planning, which helps scope out the functionality of an iteration that we have not touched on here.
- 7.
All actions that involve a card are carried out with a care that transcends its deceptive simplicity and informality. Indeed, one team studied had an internal wiki entry entitled “The care and feeding of story cards.”
- 8.
Collective ownership is part of the technical practice of XP: “Anybody who sees an opportunity to add value to any portion of the code is required to do so at any time.” [3: 59].
References
Abrahamsson P, Warsta J, Siponen MT, Ronkainen J (2003) New directions on agile methods: A comparative analysis. Proceeding of ICSE’03, ACM, New York, pp. 244–254.
Agile Manifesto http://agilemanifesto.org/, accessed 7th October 2008.
Beck K (2000) eXtreme Programming Explained: Embrace Change. San Francisco: Addison-Wesley.
Beck K, Andres C (2004) eXtreme Programming Explained: Embrace Change. San Francisco: Addison-Wesley.
Blandford A, Furniss D (2005) DiCoT: A methodology for applying distributed cognition to the design of team working systems. Proceedings of DSVIS’05, Springer, Berlin, Heidelberg, New York.
Boehm B, Turner R (2004) Balancing Agility and Discipline. Boston, MA: Addison-Wesley.
Bryant S, Romero P, du Boulay B (2008) Pair programming and the mysterious role of the navigator. IJHCS 66(7): 519–529.
Button G (2004) Changing ways of working, seminar given at the IBM Alamaden Institute, presentation available at http://www.almaden.ibm.com/institute/2004/bio/2004/index.shtml?button.
Chong J (2005) Social behaviours on XP and non-XP teams: A comparative study. Proceedings of Agile 2005, IEEE, Los Alamitos, pp. 39–48.
Cockburn A (2000) Balancing lightness with sufficiency. Cutter IT Journal 13(11): 26–33.
Cockburn A (2004) Crystal Clear: A Human-Powered Methodology for Small Teams. San Francisco: Addison Wesley.
Cohn M (2004) User Stories Applied. San Francisco: Addison-Wesley.
Davies R, Sharp H (2006) Early and often: Elaborating agile requirements. Cutter IT Journal 19(7): 6–11.
Good J, Romero P (2008) Collaborative and social aspects of software development. IJHCS 66(7): 481–483.
Green TRG, Petre M (1996) Usability analysis of visual programming environments: A ‘cognitive dimensions’ framework. Journal of Visual Languages and Computing 7: 131–174.
Highsmith J (2002) Agile Software Development Ecosystems. San Francisco: Addison-Wesley.
Iterex (2008) http://www.planningcards.com/site/, accessed 13th October 2008.
Jeffries R (2001) Essential XP: Card, Conversation, Confirmation, accessed 04.11.07 http://www.xprogramming.com/xpmag/EXPCardConversationConfirmation.htm.
Kruchten P, Adolph S (2008) Scrutinizing agile practices or shoot-out at the agile corral. Workshop at ICSE 2008, Leipzig, Germany.
MacKenzie A, Monk S (2004) From cards to code: How extreme programming re-embodies programming as a collective practice. CSCW 13: 91–117.
Mackinnon T (2003) XP – call in the social workers. In: Marchesi M, Succi G, (Eds.) Proceedings of XP2003, Lecture Notes in Computer Science, Vol. 2675. Berlin, Heidelberg, New York: Springer, pp. 288–297.
Martin A, Biddle R, Noble J (2004) The XP customer role in practice: Three case studies. Proceedings of the Second Agile Development Conference, Salt Lake City, Utah, June 22–26. IEEE, Los Alamitos.
Martin A, Noble J, Biddle R (2003) Being Jane Malkovitch: A look into the world of an XP customer. In: Marchesi M, Succi G (Eds.) Proceedings of XP2003, Lecture Notes in Computer Science, Vol. 2675. Berlin, Heidelberg, New York: Springer, pp. 234–243.
Paulk MC (2001) Extreme programming from a CMM perspective. IEEE Software, November/December 2001, pp. 19–26.
Robinson HM, Segal J, Sharp H (2007) Ethnographically-informed empirical studies of software practice. Information and Software Technology 49(6): 540–551.
Schwaber K, Beedle M (2002) Agile Software Development with SCRUM. Englewood Cliffs, NJ: Prentice Hall.
Sharp H, Robinson HM (2008) Collaboration and co-ordination in mature eXtreme programming teams. IJHCS 66: 506–518.
Sharp H, Robinson HM, Petre M (2009) The role of physical artefacts in agile software development: Two complementary perspectives. Interacting with Computers 21: 108–116.
Sharp H, Robinson HM, Segal J (2004) eXtreme programming and user-centered design: Friend or foe? Proceeding of HCI2004, Leeds.
Weinberg G (1998) The Psychology of Computer Programming. New York: Dorset House.
Whitworth E, Biddle R (2007) The social nature of Agile teams. Proceedings of Agile 2007, Washington, DC, August, IEEE, Los Alamitos, pp. 13–17.
Author information
Authors and Affiliations
Corresponding author
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2010 Springer-Verlag Berlin Heidelberg
About this chapter
Cite this chapter
Robinson, H., Sharp, H. (2010). Collaboration, Communication and Co-ordination in Agile Software Development Practice. In: Mistrík, I., Grundy, J., Hoek, A., Whitehead, J. (eds) Collaborative Software Engineering. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-10294-3_5
Download citation
DOI: https://doi.org/10.1007/978-3-642-10294-3_5
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-10293-6
Online ISBN: 978-3-642-10294-3
eBook Packages: Computer ScienceComputer Science (R0)