How Do Globally Distributed Agile Teams Self-organise? - Initial Insights from a Case Study

Sherlock A. Licorish, Stephen G. MacDonell


Agile software developers are required to self-organize, occupying various informal roles as needed in order to successfully deliver software features. However, previous research has reported conflicting evidence about the way teams actually undertake this activity. The ability to self-organize is particularly necessary for software development in globally distributed environments, where distance has been shown to exacerbate human-centric issues. Understanding the way successful teams self-organise should inform distributed team composition strategies and software project governance. We have used psycholinguistics to study the way IBM Rational Jazz practitioners enacted various roles, expressed attitudes and shared competencies to successfully self-organize in their global projects. Among our findings, we uncovered that practitioners enacted various roles depending on their teams’ cohort of features; and that team leaders were most critical to IBM Jazz teams’ self-organisation. We discuss these findings and highlight their implications for software project governance.


  1. Abrahamsson, P., Marchesi, M., Succi, G., Sfetsos, P., Stamelos, I., Angelis, L. & Deligiannis, I. 2006. Investigating the Impact of Personality Types on Communication and Collaboration-Viability in Pair Programming - An Empirical Study. Extreme Programming and Agile Processes in Software Engineering. Springer Berlin / Heidelberg.
  2. Acuna, S. T., Juristo, N. & Moreno, A. M. 2006. Emphasizing human capabilities in software development. IEEE Software, 23, 94 - 101.
  3. Andre, M., Baldoquin, M. G. & Acuna, S. T. 2011. Formal model for assigning human resources to teams in software projects. I&ST, 53, 259-275.
  4. Ashforth, B. E. 2001. Role transitions in organizational life: An identity based perspective, Mahwah, NJ: Lawrence Earlbaum.
  5. Batson, C. D., Ahmad, N. & Tsang, J. A. 2002. Four Motives for Community Involvement. Journal of Social Issues, 58, 429-445.
  6. Belbin, R. M. 2002. Management teams: why they succeed or fail., Woburn, UK, Butterworth-Heinemann.
  7. Benne, K. D. & Sheats, P. 1948. Functional Roles of Group Members. Journal of Social Issues, 4, 41-49.
  8. Biddle, B. J. & Thomas, E. J. 1966. Role theory: Concepts and research, New York: John Wiley & Sons.
  9. Downey, J. 2009. Designing Job Descriptions for Software Development. Info. Sys. Dev.: Challenges in Practice, Theory, and Education. USA: Springer US.
  10. Espinosa, J. A., Delone, W. & Lee, G. 2006. Global boundaries, task processes and IS project success: a field study. Info. Tech. & People, 19, 345 - 370.
  11. Frost, R. 2007. Jazz and the Eclipse Way of Collaboration. IEEE Softw., 24, 114-117.
  12. Glaser, B. G. & Strauss, A. L. 1967. The Discovery of Grounded Theory: Strategies for Qualitative Research, Chicago, Aldine Publishing Company.
  13. Goldberg, L. R. 1981. Language and individual differences: The search for universals in personality lexicons. Review of Pers. & Soc.Psyc., 2, 141-165.
  14. Gonzales, A. L., Hancock, J. T. & Pennebaker, J. W. 2010. Language Style Matching as a Predictor of Social Dynamics in Small Groups. Communication Research, 37, 3-19.
  15. Gorla, N. & Lam, Y. W. 2004. Who should work with whom?: building effective software project teams. Commun. ACM, 47, 79-82.
  16. Hellriegel, D. & Slocum, J. W. 2007. Organizational Behavior, Mason, OH: Thomson Learning.
  17. Highsmith, J. 2004. Agile Project Management: Creating Innovative Products., Boston, MA, Pearson Education.
  18. Hoda, R., Noble, J. & Marshall, S. 2010. Organizing self-organizing teams. Proceedings of the 32nd ACM/IEEE ICSE - Volume 1. Cape Town, South Africa: ACM.
  19. Licorish, S., Philpott, A. & Macdonell, S. G. 2009 Supporting agile team composition: A prototype tool for identifying personality (In)compatibilities. ICSE Workshop on CHASE. Vancouver, Canada: IEEE Computer Society.
  20. Mairesse, F., Walker, M., Mehl, M. R. & Moore, R. K. 2007. Using linguistic cues for the automatic recognition of personality in conversation and text. J. Artif. Int. Res., 30, 457-500.
  21. Moe, N. B., Dingsoyr, T. & Dyba, T. 2008. Understanding Self-Organizing Teams in Agile Software Development. Proceedings of the 19th ASWEC. Perth, WA: IEEE Computer Society.
  22. Pennebaker, J. W. & King, L. A. 1999. Linguistic Styles: Language Use as an Individual Difference. Journal of Personality & Social Psychology, 77, 1296-1312.
  23. Pennebaker, J. W. & Lay, T. C. 2002. Language Use and Personality during Crises: Analyses of Mayor Rudolph Giuliani's Press Conferences. Journal of Research in Personality, 36, 271-282.
  24. Pennebaker, J. W., Mehl, M. R. & Niederhoffer, K. G. 2003. Psychological Aspects of Natural Language Use: Our Words, Our Selves. Annual Review of Psychology, 54, 547-577.
  25. Pressman, R. S. 2009. Software Engineering: A Practitioner's Approach, New York, McGraw-Hill.
  26. Rigby, P. & Hassan, A. E. 2007. What Can OSS Mailing Lists Tell Us? A Preliminary Psychometric Text Analysis of the Apache Developer Mailing List. Proceedings of the 4th MSR. Minneapolis, MN: IEEE Computer Society.
  27. Serce, F. C., Alpaslan, F.-N., Swigger, K., Brazile, R., Dafoulas, G., Lopez, V. & Schumacker, R. 2009. Exploring Collaboration Patterns among Global Software Development Teams. Proceedings of the 4th ICGSE. IEEE Computer Society.
  28. Standish Group 2009. CHAOS Summary 2009. West Yarmouth, MA: The Standish Group International Inc.
  29. Trigo, A., Varajao, J., Soto-Acosta, P., Barroso, J., Molina-Castillo, F. J. & Gonzalvez-Gallego, N. 2010. IT professionals: an Iberian snapshot. IJHCITP, 1, 61- 75.
  30. Zhu, E. 1996. Meaning Negotiation, Knowledge Construction, and Mentoring in a Distance Learning Course. In: Presentations at the National Convention of the Association for Educational Communications and Technology, 1996 Indianapolis, USA. Education Research Information Center, 821-844.

Paper Citation

in Harvard Style

Licorish S. and MacDonell S. (2013). How Do Globally Distributed Agile Teams Self-organise? - Initial Insights from a Case Study . In Proceedings of the 8th International Conference on Evaluation of Novel Approaches to Software Engineering - Volume 1: ENASE, ISBN 978-989-8565-62-4, pages 157-164. DOI: 10.5220/0004437001570164

in Bibtex Style

author={Sherlock A. Licorish and Stephen G. MacDonell},
title={How Do Globally Distributed Agile Teams Self-organise? - Initial Insights from a Case Study},
booktitle={Proceedings of the 8th International Conference on Evaluation of Novel Approaches to Software Engineering - Volume 1: ENASE,},

in EndNote Style

JO - Proceedings of the 8th International Conference on Evaluation of Novel Approaches to Software Engineering - Volume 1: ENASE,
TI - How Do Globally Distributed Agile Teams Self-organise? - Initial Insights from a Case Study
SN - 978-989-8565-62-4
AU - Licorish S.
AU - MacDonell S.
PY - 2013
SP - 157
EP - 164
DO - 10.5220/0004437001570164