Role of collective ownership and coding standards in coordinating expertise in software project teams

European Journal of Information Systems

Volumn 18, Issue 4, 2009, Pages 355-371

  Maruping, Likoebe M ^a   Zhang, Xiaojun ^a   Venkatesh, Viswanath ^a  

^a UNIVERSITY OF ARKANSAS   (United States)

Author keywords

Agile development; Agile methodology; Coding standards; Collective ownership; EXtreme programming; Software development teams; Software project performance; XP

Indexed keywords

EID: 70149118164     PISSN: 0960085X     EISSN: 14769344     Source Type: Journal    
DOI: 10.1057/ejis.2009.24     Document Type: Article

References (97)

1. ABRAHAMSSON P and KOSKELA J (2004). Extreme programming: a survey of empirical data from a controlled case study. In Proceedings of the ACM-IEEE International Symposium on Empirical Software Engineering (JURISTO, F and SHULL, F, Eds), pp. 73-82, IEEE Computer Society Press, Redondo Beach, CA. (Pubitemid 40062820)
2. AIKEN LS and WEST SG (1991) Multiple Regression: Testing and Interpreting Interactions. Sage, London.
3. AKGUN AE, BYRNE JC, KESKIN H and LYNN GS (2006) Transactive memory system in new product development teams. IEEE Transactions on Engineering Management 53(1), 95-111.
4. ANCONA DG and CALDWELL D (1992) Bridging the boundary: external activity and performance in organizational teams. Administrative Science Quarterly 37(4), 634-665.
5. ARGOTE L (1982) Input uncertainty and organizational coordination in hospital emergency units. Administrative Science Quarterly 27(3), 420-434.
6. BAHLI B and ZEID ESA (2005) The role of knowledge creation in adopting extreme programming model: an empirical study. In ITI 3rd International Conference on Information and Communications Technology: Enabling Technologies for the New Knowledge Society, pp 75-87, IEEE Computer Press, Cairo, Egypt.
7. BALIJEPALLY V, MAHAPATRA R, NERUR S and PRICE KH (2009) Are two heads better than one for software development? The productivity paradox of pair programming. MIS Quarterly 33(1), 91-188.
8. BANKER RD, DAVIS GB and SLAUGHTER SA (1998) Software development practices, software complexity, and software maintenance performance: a field study. Management Science 44(4), 433-450.
9. BANKER RD and SLAUGHTER SA (2000) The moderating effect of structure on volatility and complexity in software enhancement. Information Systems Research 11(3), 219-240.
10. BARRY EJ, KEMERER CF and SLAUGHTER SA (2006) Environmental volatility, development decisions, and software volatility: a longitudinal analysis. Management Science 52(3), 448-464.
11. BASKERVILLE R, LEVINE L, PRIES-HEJE J, RAMESH B and SLAUGHTER SA (2002) Balancing quality and agility in Internet speed software development. In Proceedings of the 23rd International Conference on Information Systems (APPLEGATE L, GALLIERS R and DEGROSS JI, Eds), pp 859-864, Association for Information System Press, Barcelona, Spain.
12. BECK K (1999) Embracing change with extreme programming. IEEE Computer 32(10), 70-77.
13. BECK K (2000) Extreme Programming Explained. Addison-Wesley, Reading, MA.
14. BECK K (2003) Test-Driven Development by Example. Addison-Wesley, Reading, MA.
15. BIEMAN J (2002) Risks to software quality. Software Quality Journal 10(1), 7-9.
16. BLIESE PD (2000) Within-group agreement, non-independence, and reliability: implications for data aggregation and analysis. In Multilevel Theory, Research, and Methods in Organizations (KLEIN KJ and KOZLOWSKI SWJ Eds), pp 349-381, Jossey-Bass, San Fransisco, CA.
17. BOEHM B and TURNER R (2005) Management challenges to implementing agile processes in traditional development organizations. IEEE Software 22(5), 30-39.
18. BOH WF, REN Y, KIESLER S and BUSSKAEGER R (2007) Expertise and collaboration in the geographically dispersed organization. Organization Science 18(4), 595-612.
19. BOLAND RJ and TENKASI RV (1995) Perspective making and perspective taking in communities of knowing. Organization Science 6(4), 350-372.
20. CARMEL E, WHITAKER R and GEORGE J (1993) PD and joint application design: a transatlantic comparison. Communications of the ACM 36(4), 40-48.
21. CHAN D (1998) Functional relations among constructs in the same content domain at different levels of analysis: a typology of composition models. Journal of Applied Psychology 83(2), 234-246.
22. CHONG J (2005) Social behaviors on XP and non-XP teams: a comparative study. In Proceedings of the Agile Development Conference (ADC?05).
23. COAD P, DE LUCA J and LEFEBRE E (1999) Java Modeling in Color. Prentice-Hall, Englewood Cliffs, NJ.
24. COCKBURN A (2001) Agile Software Development. Addison-Wesley, Reading, MA.
25. COHEN S and BAILEY D (1997) What makes teams work? Group effectiveness research from the shop floor to the executive suite. Journal of Management 23(3), 239-290.
26. CONBOY K (2009) Agility from first principles: reconceptualizing the concept of agility in information systems development. Information Systems Research 20(3), in press.
27. 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.
28. CUSUMANO M, MACCORMACK A, KEMERER C and CRANDALL B (2003) Software development worldwide: the state of the practice. Communications of the ACM 20(6), 28-34.
29. DANSEREAU F, ALUTTO JA and YAMMARINO FJ (1984) Theory Testing in Organizational Behavior: The Variant Approach. Prentice-Hall, Engle-wood Cliffs, NJ.
30. DEVELLIS RF (2003) Scale Development: Theory and Applications. Sage, Thousand Oaks, CA.
31. DYBA T and DINGSOYR T (2008) Empirical studies of agile software development: a systematic review. Information & Software Technology 50(9-10), 833-859.
32. ERDOGMUS H and WILLIAMS L (2003) The economics of software development by pair programmers. The Engineering Economist 48(4), 283-319.
33. ERICKSON J, LYYTINEN K and SIAU K (2005) Agile modeling, agile software development, and extreme programming: the state of research. Journal of Database Management 16(4), 88-99.
34. ESPINOSA JA, KRAUT RE, LERCH J, SLAUGHTER SA, HERBSLEB J and MOCKUS A (2001) Shared mental models and coordination in large-scale, distributed software development. In Proceedings of the 22nd International Conference on Information Systems, pp 513-517, Association for Information Systems Press, New Orleans, LA.
35. ESPINOSA JA, SLAUGHTER SA, KRAUT RE and HERBSLEB JD (2007a) Team knowledge and coordination in geographically distributed software development. Journal of Management Information Systems 24(1), 135-169.
36. ESPINOSA JA, SLAUGHTER SA, KRAUT RE and HERBSLEB JD (2007b) Familiarity, complexity, and team performance in geographically distributed software development. Organization Science 18(4), 613-630.
37. FARAJ S and SPROULL L (2000) Coordinating expertise in software development teams. Management Science 46(12), 1554-1568.
38. FITZGERALD B (2000) Systems development methodologies: the problem of tenses. Information Technology and People 13(3), 13-22.
39. FITZGERALD B, HARTNETT G and CONBOY K (2006) Customising agile methods to software practices at Intel Shannon. European Journal of Information Systems 15(2), 200-213.
40. FITZGERALD B, RUSSO N and O?KANE T (2003) Software development method tailoring at Motorola. Communications of the ACM 46(4), 64-70.
41. FOWLER M and HIGHSMITH J (2001) Agile methodologists agree on something. Software Development 9, 28-32.
42. FRY LW and SLOCUM JW (1984) Technology, structure, and work group effectiveness: a test of a contingency model. Academy of Management Journal 27(2), 221-246.
43. GRENNING J (2001) Launching extreme programming at a process intensive company. IEEE Software 16(8), 27-33.
44. HIGHSMITH J and COCKBURN A (2001) Agile software development: the business of innovation. IEEE Computer 34(9), 120-122.
45. HOLMSTROM H, FITZGERALD B, AGERFALK PJ and CONCHUIR EO (2006) Agile practices reduce distance in global software development. Information Systems Management 23(3), 7-18.
46. IANSITI M and MACCORMACK A (1997) Developing products on Internet time. Harvard Business Review 75(5), 108-117.
47. IIVARI J, HIRSCHHEIM R and KLEIN HK (1998) A paradigmatic analysis contrasting information systems development approaches and methodologies. Information Systems Research 9(2), 164-193.
48. IIVARI J and HUISMAN M (2007) The relationship between organizational culture and the deployment of systems development methodologies. MIS Quarterly 31(1), 35-58.
49. ILGEN DR, HOLLENBECK JR, JOHNSON M and JUNDT D. (2005) Team in organizations: from input-process-output models to IMOI models. Annual Review of Psychology 56, 517-543.
50. ILIEVA S, IVANOV P and STEFANOVA E (2004) Analyses of an agile methodology implementation. In Proceedings of the 30th Euromicro Conference, pp 326-333, IEEE Computer Society Press, Rennes, France.
51. JEFFRIES R, ANDERSON A and HENDRICKSON C (2000) Extreme Programming Installed. Addison-Wesley, Boston, MA.
52. JI Y, MOOKERJEE VS and SETHI SP (2005) Optimal software development: a control theoretic approach. Information Systems Research 16(3), 292-306.
53. JOHNS G (2006) The essential impact of context on organizational behavior. Academy of Management Review 31(2), 386-408.
54. KARLSSON E, ANDERSSON L and LEION P (2000) Daily build and feature development in large distributed projects. In Proceedings of the International Conference on Software Engineering, pp 649-658, ACM Press Limerick, Ireland.
55. KLEIN KJ, DANSEREAU F and HALL RJ (1994) Levels issues in theory development, data collection, and analysis. Academy of Management Review 19(2), 195-229.
56. KLEIN KJ and KOZLOWSKI SWJ (2000) From micro to meso: critical steps in conceptualizing and conducting multilevel research. Organizational Research Methods 3(3), 211-236.
57. KRAUT R and STREETER L (1995) Coordination in software development. Communications of the ACM 38(3), 69-81.
58. LARMAN C (2003) Agile and Iterative Development: A Manager?s Guide. Addison-Wesley, Reading, MA.
59. LEE G and XIA W (2005) The ability of information systems development project teams to respond to business and technology changes: a study of flexibility measures. European Journal of Information Systems 14(1), 75-92.
60. LEPINE JA, PICCOLO RF, JACKSON CL, MATHIEU JE and SAUL JR (2008) A meta-analysis of teamwork processes: tests of a multidimensional model and relationships with team effectiveness criteria. Personnel Psychology 61(2), 273-307.
61. LEWIS K (2003) Measuring transactive memory systems in the field: scale development and validation. Journal of Applied Psychology 88(4), 587-604.
62. LUI K and CHAN K (2006) Pair programming productivity: novice-novice vs expert-expert. International Journal of Human-Computer Studies 64(9), 915-925.
63. MARKS MA, MATHIEU JE and ZACCARO SJ (2001) A temporally based framework and taxonomy of team processes. Academy of Management Review 26(3), 356-376.
64. MARTIN RC (2002) Agile Software Development, Principles, Patterns, and Practices. Prentice-Hall, Englewood Cliffs, NJ.
65. MARUPING LM, VENKATESH V and AGARWAL R (2009) A control theory perspective on agile methodology use and changing user requirements. Information Systems Research 20(3), in press.
66. MORELAND RL and MYASKOVSKY L (2000) Exploring the performance benefits of group training: transactive memory or improved communication? Organizational Behavior and Human Decision Processes 82(1), 117-133.
67. MORGESON FP and HOFMANN DA (1999) The structure and function of collective constructs: implications for multilevel research and theory development. Academy of Management Review 24(2), 249-265.
68. MURRU O, DEIAS R and MUGHEDDU G (2003) Assessing XP at a European Internet company. IEEE Software 20(3), 37-43.
69. NERUR S, MAHAPATRA R and MANGALARAJ G (2005) Challenges of migrating to agile methodologies. Communications of the ACM 48(5), 72-78.
70. NONAKA IH and TAKEUCHI HA (1995) The Knowledge-Creating Company. Oxford University Press, Oxford, U.K.
71. NORTH AMERICAN and EUROPEAN ENTERPRISE SOFTWARE and SERVICES SURVEY (2005). Corporate IT Leads the Second Wave of Agile Adoption. Forrester Research Inc. pp 1-6.
72. NOSEK J (1998) The case for collaborative programming. Communications of the ACM 41(3), 105-108.
73. ORLIKOWSKI W and IACONO S (2001) Research commentary: desperately seeking the ?IT? in IT research - a call to theorizing about the IT artifact. Information Systems Research 12(2), 121-134.
74. PANKO RR (1999) Applying code inspection to spreadsheet testing. Journal of Management Information Systems 16(2), 159-176.
75. PERLOW L, GITTELL J and KATZ N (2004) Contextualizing patterns of work group interaction: toward a nested theory of structuration. Organization Science 15(5), 520-536.
76. PIKKARAINEN M, WANG X and CONBOY K (2007) Agile practices in use from an innovation assimilation perspective: a multiple case study. In Proceedings of the 28th International Conference on Information Systems, pp 1-17, Association for Information Systems Press, Montreal, Canada.
77. PODSAKOFF PM, MACKENZIE SB, LEE JY and PODSAKOFF NP (2003) Common method biases in behavioral research: a critical review of the literature and recommended remedies. Journal of Applied Psychology 88(5), 879-903.
78. POOLE C and HUISMAN JW (2001) Using extreme programming in a maintenance environment. IEEE Software 18(6), 42-50.
79. POPPENDEICK M (2001) Lean programming. Software Development 9(5), 71-75.
80. REAGANS R and MCEVILY B (2003) Network structure and knowledge transfer: the effects of cohesion and range. Administrative Science Quarterly 48(2), 240-267.
81. REN Y, CARLEY KM and ARGOTE L (2006) The contingent effects of transactive memory: when is it more beneficial to know what others know? Management Science 52(5), 671-682.
82. RICO DF (2008) Effects of agile methods on website quality for electronic commerce. In Proceedings of the 41st Annual Hawaii International Conference on System Science, p 464, IEEE Computer Society Press, Waikaloa, Big Island, Hawaii.
83. RISING L and JANOFF NS (2000) The Scrum software development process for small teams. IEEE Software 17(4), 26-32.
84. SALAS E, SIMS DE and BURKE CS (2005) Is there a ?Big Five? in teamwork? Small Group Research 36(5), 555-599.
85. SCHUH P (2001) Recovery, redemption, and extreme programming. IEEE Software 18(6), 33-40.
86. SCHWABER K and BEEDLE M (2002) Agile Software Development with Scrum. Prentice-Hall, Upper Saddle River, NJ.
87. STANDISH GROUP (2003) The Standish Group report.
88. STRAUB DW (1989) Validating instruments in MIS research. MIS Quarterly 13(2), 147-169.
89. THOMPSON J (1967) Organizations in Action. McGraw-Hill, New York.
90. TURK D, FRANCE R and RUMPE B (2005) Assumptions underlying agile software development process. Journal of Database Management 16(4), 62-87.
91. WALZ DB, ELAM JJ and CURTIS B (1993) Inside a software design team: knowledge acquisition, sharing, and integration. Communications of the ACM 36(10), 63-77.
92. WEGNER DM (1986) Transactive memory: a contemporary analysis of the group mind. In Theories of Group Behavior (MULLEN B and GOETHALS GR, Eds), pp 185-205, Springer-Verlag, New York.
93. WEGNER DM (1995) A computer network model of human transactive memory. Social Cognition 13(3), 319-339.
94. WEGNER DM, ERBER and RAYMOND P (1991) Transactive memory in close relationships. Journal of Personality and Social Psychology 61(6), 923-929.
95. WILLIAMS L and KESSLER R (2000) All I really need to know about pair programming I learned in kindergarten. Communications of the ACM 43(5), 109-114.
96. WILLIAMS L and KESSLER R (2001) Experimenting with industry?s ?pair-programming? model in the computer science classroom. Computer Science Education 11(1), 7-20.
97. WOOD J and SILVER D (1989) Joint Application Design: How to Design Quality Systems in 40% Less Time. Wiley, New York.