Coordination effectiveness in an agile software development context

PACIS 2011 - 15th Pacific Asia Conference on Information Systems: Quality Research in Pacific

Volumn , Issue , 2011, Pages

  Strode, Diane E ^a   Hope, Beverley ^a   Huff, Sid L ^a   Link, Sebastian ^a  

^a VICTORIA UNIVERSITY OF WELLINGTON   (New Zealand)

Author keywords

Agile software development project; Coordination effectiveness; Coordination strategy

Indexed keywords

AGILE SOFTWARE DEVELOPMENT; COORDINATION EFFECTIVENESS; COORDINATION STRATEGY; SOFTWARE PROJECT; SYSTEM DEVELOPMENT METHODOLOGIES;

AGILE MANUFACTURING SYSTEMS; COMPUTER SOFTWARE SELECTION AND EVALUATION; INFORMATION SYSTEMS; RESEARCH;

SOFTWARE DESIGN;

EID: 84855825315     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: None     Document Type: Conference Paper

References (63)

1. Abrahamsson, P., Conboy, K. and Wang, X. (2009). 'Lots done, more to do': the current state of agile systems development research. European Journal of Information Systems, 18(4), 281-284.
2. Abrahamsson, P., Warsta, J., Siponen, M. K. and Ronkainen, J. (2003). New directions on agile methods: A comparative analysis Proceedings of the 25th International Conference on Software Engineering, ICSE'03 (pp. 244-254). Washington, DC, USA: IEEE Computer Society.
3. Agerfalk, P. J., Fitzgerald, B. and Slaughter, S. A. (2009). Flexible and distributed information systems development: state of the art and research challenges. Information Systems Research, 20(3), 317-328.
4. Ambler, S. (2008). Agile adoption rate survey: February 2008 Retrieved 25 February, 2009, from http://www.ambysoft.com/surveys/
5. Andres, H. P. and Zmud, R. W. (2001). A contingency approach to software project coordination. Journal of Management Information Systems, 18(3), 41-70. (Pubitemid 34048270)
6. Avison, D. and Fitzgerald, G. (2006). Information systems development: methodologies, techniques and tools (4 ed.). London: McGraw-Hill.
7. Bacharach, S. B. (1989). Organizational theories: some criteria for evaluation. The Academy of Management Review, 14(4), 496-515.
8. Barki, H., Rivard, S. and Talbot, J. (2001). An integrative contingency model of software project risk management. Journal of Management Information Systems, 17(4), 37-69. (Pubitemid 32716733)
9. Baskerville, R., Pries-Heje, J. and Ramesh, B. (2007). The enduring contradictions of new software development approaches: a response to 'persistent problems and practices in ISD'. Information Systems Journal, 17, 241-245.
10. Beck, K., Beedle, M., van Bennekum, A., Cockburn, A., Cunningham, W., Fowler, M. et al. (2001). Manifesto for agile software development Retrieved 17 February, 2003, from http://www.agilemanifesto.org.
11. Cao, L. and Ramesh, B. (2007, March April). Agile software development: ad hoc practices or sound principles? IT Pro, 41-47. (Pubitemid 46548994)
12. Conboy, K. (2009). Agility from first principles: reconstructing the concept of agility in information systems development. Information Systems Research, 20(3), 329-354.
13. Conboy, K., Fitzgerald, B., and Golden, W. (2005). Agility in information systems development: a three-tiered framework. In R. Baskerville, L. Mathiassen, J. Pries-Heje & J. DeGross (Eds.), Business agility and information technology diffusion IFIP TC8 WG 8.6 International Working Conference May 8-11, 2005, Atlanta, Georgia, U.S.A. ( 36-49). New York: Springer.
14. Crowston, K. (1991). Towards a coordination cookbook: recipes for multi-agent action. PhD, Massachusetts Institute of Technology. Retrieved from http://www.archive.org/details/towardscoordinat00crow.
15. Crowston, K. (2003). A taxonomy of organizational dependencies and coordination mechanisms. In T. W. Malone, K. Crowston & G. A. Herman (Eds.), Organizing business knowledge: the MIT process handbook ( 86-108). Cambridge, Massachusetts: The MIT Press.
16. Crowston, K., Rubleske, J. and Howison, J. (2006). Coordination theory: a ten-year retrospective. In P. Zhang & D. Galletta (Eds.), Human-Computer Interaction and Management Information Systems: Foundations ( 120-138). Armonk, New York: Sharpe, M E.
17. Curtis, B., Krasner, H. and Iscoe, N. (1988). A field study of the software design process for large systems. Communications of the ACM, 31(11), 1268-1287.
18. Darke, P., Shanks, G. and Broadbent, M. (1998). Successfully completing case study research: Combining rigour, relevance and pragmatism. Information Systems Journal, 8(4), 273-289.
19. Dingsoyr, T., Dyba, T. and Abrahamsson, P. (2008). A preliminary roadmap for empirical research on agile software development. Proceedings of the Agile 2008 Conference, 83-94.
20. Dube, L. and Pare, G. (2003). Rigor in information systems positivist case research: Current practice, trends, and recommendations. MIS Quarterly, 27(4), 597-635.
21. Dyba, T. and Dingsoyr, T. (2008). Empirical studies of agile software development: a systematic review. Information and Software Technology, 50(9-10), 833-859.
22. Eisenhardt, K.M. (1989). Building theories from case study research. The Academy of Management Review, 14(4), 532-550.
23. Eisenhardt, K. M. and Graebner, M. E. (2007). Theory building from cases: opportunities and challenges. Academy of Management Journal, 50(1), 25-32.
24. Espinosa, A., Lerch, J. and Kraut, R. (2002). Explicit vs. Implicit coordination mechanisms and task dependencies: one size does not fit all. Retrieved 29 May 2010, 2010, from http://www.cs.cmu.edu/afs/cs.cmu.edu/user/ kraut/www/RKraut.site.files/articles/Espinosa03-ExplicitVsImplicitCoordination. pdf.
25. Faraj, S. and Sproull, L. (2000). Coordinating expertise in software development teams. Management Science, 46(12), 1554-1568. (Pubitemid 32138391)
26. Fiore, S. and Salas, E. (2004). Why we need team cognition. In E. Salas & S. M. Fiore (Eds.), Team cognition (pp. 235-248). Washington, DC: American Psychological Association.
27. Fitzgerald, B., Hartnett, G. and Conboy, K. (2006). Customising agile methods to software practices at Intel Shannon. European Journal of Information Systems, 15, 200-213. (Pubitemid 44022574)
28. Fruhling, A. and de Vreede, G.-J. (2006). Field experiences with eXtreme programming: developing an emergency response system. Journal of Management Information Systems, 22(4), 39-68. (Pubitemid 44377671)
29. Galbraith, J. R. (1977). Organization design. Reading, MA: Addison-Wesley.
30. Gregor, S. (2006). The nature of theory in information systems. MIS Quarterly, 30(3), 611-642. (Pubitemid 46061265)
31. Harris, M. L., Collins, R. W. and Hevner, A. R. (2009). Control of flexible software development under uncertainty. Information Systems Research, 20(3), 400-419.
32. Hilkka, M.-R., Tuure, T. and Matti, R. (2005). Is extreme programming just old wine in new bottles: a comparison of two cases. Journal of Database Management, 16(4), 41-61. (Pubitemid 41491484)
33. Iivari, J., Hirschheim, R. and Klein, H. K. (2004). Towards a distinct body of knowledge for Information Systems experts: Coding ISD process knowledge in two IS journals. Information Systems Journal, 14(4), 313-342. (Pubitemid 39285228)
34. Kotlarsky, J., van Fenema, P. C. and Willcocks, L. P. (2008). Developing a knowledge-based perspective on coordination: the case of global software projects. Information and Management, 45, 96-108. (Pubitemid 351324048)
35. Kraut, R. E. and Streeter, L. A. (1995). Coordination in software development. Communications of the ACM, 38(3), 69-81.
36. Lawrence, P. R. and Lorsch, J. W. (1967). Differentiation and integration in complex organisations. Administrative Science Quarterly, 12, 1-47.
37. MacKenzie, A. and Monk, S. (2004). From cards to code: how extreme programming re-embodies programming as collective practice. Computer Supported Cooperative Work, 13(1), 91-117.
38. Madsen, S. (2007). Conceptualising the causes and consequences of uncertainty in IS development organisations and projects. Paper presented at the 15th European Conference on Information Systems, St. Gallen, Switzerland.
39. Malone, T. W. (1987). Modeling coordination in organizations and markets. Management Science, 33(10), 1317-1332.
40. Malone, T. W. (1988). What is coordination theory? Retrieved from http://hdl.handle.net/1721.1/2208.
41. Malone, T. W. and Crowston, K. (1994). The interdisciplinary study of coordination. ACM Computing Surveys, 26(1), 87-119.
42. March, J. G. and Simon, H. A. (1958). Organization. New York: Wiley.
43. Maruping, L. M., Venkatesh, V. and Agarwal, R. (2009). A control theory perspective on agile methodology use and changing user requirements. Information Systems Research, 20(3), 277-399.
44. McChesney, I. R. and Gallagher, S. (2004). Communication and coordination practices in software engineering projects. Information and Software Technology, 46(7), 473-489.
45. Miles, M. B. and Huberman, A. M. (1994). Qualitative data analysis (2 ed.). Thousand Oaks: SAGE Publications Inc.
46. Mintzberg, H. (1980). Structure in 5's: a synthesis of the research on organization design. Management Science, 26(3), 322-341.
47. Mohammed, S., Ferzandi, L. and Hamilton, K. (2010). Metaphor no more: a 15-year review of the team mental model construct. Journal of Management, 36(4), 876-910.
48. Nerur, S. and Balijepally, V. (2007). Theoretical reflections on agile development methodologies. Communications of the ACM, 50(3), 79-83. (Pubitemid 46555347)
49. Nidumolu, S. (1995). The effect of coordination and uncertainty on software project performance: residual performance risk as an intervening variable. Information Systems Research, 6(3), 191-219. (Pubitemid 126102979)
50. Olle, T. W., Sol, H. C. and Tully, C. (Eds.). (1983). Information systems design methodologies: A feature analysis. Proceedings of the IFIP WB 8.1 Working Conference on Feature Analysis of Information Systems Design Methodologies. Amsterdam: North-Holland.
51. Pare, G. (2004). Investigating information systems with positivist case study research. Communications of the Association for Information Systems, 13, 233-264.
52. Rajlich, V. (2006). Changing the paradigm of software engineering. Communications of the ACM, 49(8), 67-70. (Pubitemid 44232128)
53. Rico, R., Sanchez-Manzanares, M., Gil, F. and Gibson, C. (2008). Team implicit coordination processes: a team knowledge-based approach. Academy of Management Review, 33(1), 163-184.
54. Sarker, S., Munson, C. L., Sarker, S. and Chakraborty, S. (2009). Assessing the relative contribution of the facets of agility to distributed systems development success: an analytic hierarchy process approach. European Journal of Information Systems 18(1), 285-299.
55. Sarker, S. and Sarker, S. (2009). Exploring agility in distributed information systems development teams: an interpretive study in and offshoring context. Information Systems Research, 20(3), 440- 461.
56. Sharp, H. and Robinson, H. (2004). An ethnographic study of XP practice. Empirical Software Engineering, 9(4), 353-375.
57. Spradley, J. P. (1979). The ethnographic interview. New York: Holt, Rinehart and Winston.
58. Suddaby, R. (2010). Editor's comments: construct clarity in theories of management and organisation. Academy of Management Review, 35(3), 346-357.
59. Thompson, J. D. (1967). Organization in Action. Chicago: McGraw-Hill.
60. Van de Ven, A. H., Delbecq, A. L. and Koenig, R. (1976). Determinants of coordination modes within organizations. American Sociological Review, 41(2), 322-338.
61. Weick, K. E. and Roberts, K. H. (1993). Collective mind in organizations: heedful interrelating on flight decks. Administrative Science Quarterly, 38(3), 357-381.
62. Xia, W. and Lee, G. (2005). Complexity of Information systems development projects: conceptualization and measurement development. Journal of Management Information Systems, 22(1), 45-83. (Pubitemid 41136750)
63. Yin, R. K. (2003). Case study research (3 ed.). Thousand Oaks: Sage Publications.