On the perceived interdependence and information sharing inhibitions of enterprise software engineers

Proceedings of the ACM Conference on Computer Supported Cooperative Work, CSCW

Volumn , Issue , 2012, Pages 1337-1346

  Grubb, Alicia M ^a   Begel, Andrew ^b  

^a UNIVERSITY OF TORONTO   (Canada)

^b MICROSOFT RESEARCH   (United States)

Author keywords

awareness; communication; coordination; enterprise software development

Indexed keywords

AWARENESS; COMMUNICATION PRACTICES; COORDINATION; ENGINEERING ACTIVITIES; ENTERPRISE SOFTWARE; ENTERPRISE SOFTWARE DEVELOPMENT; INFORMATION SHARING; MICROSOFT; ORGANIZATIONAL CHARACTERISTICS; SOFTWARE ENGINEERS; SOFTWARE TEAMS; WORKGROUPS;

COMMUNICATION; COMPUTER SUPPORTED COOPERATIVE WORK; ENGINEERS; INDUSTRY; INTERACTIVE COMPUTER SYSTEMS; SOFTWARE ENGINEERING; VISUALIZATION;

ENGINEERING;

EID: 84858215551     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1145/2145204.2145403     Document Type: Conference Paper

References (53)

1. Ancona, D. G., and Caldwell, D. F. Bridging the boundary: External activity and performance in organizational teams. Administrative Science Quarterly 37, 4 (1992), pp. 634-665.
2. Anvik, J., and Murphy, G. C. Reducing the effort of bug report triage: Recommenders for development-oriented decisions. IEEE TSEM 20, 3 (2011).
3. Aranda, J., and Venolia, G. The secret life of bugs: Going past the errors and omissions in software repositories. Proc. ICSE '09, 298-308.
4. Bacchelli, A., Lanza, M., and Robbes, R. Linking e-mails and source code artifacts. Proc. ICSE '10, 375.
5. Begel, A. Effecting change: coordination in large-scale software development. Proc. CHASE '08, 17-20.
6. Begel, A., Khoo, Y. P., and Zimmerman, T. Codebook: Discovering and Exploiting Relationships in Software Repositories. Proc. ICSE '10.
7. Begel, A., Nagappan, N., Poile, C., and Layman, L. Coordination in large-scale software teams. Proc. CHASE '09, 1-7.
8. Biehl, J. T., Czerwinski, M., Smith, G., and Robertson, G. G. Fastdash: a visual dashboard for fostering awareness in software teams. Proc. CHI '07, 1313-1322.
9. Brown, S. L., and Eisenhardt, K. M. Product development: Past research, present findings, and future directions. The Academy of Management Review 20, 2 (1995), pp. 343-378.
10. Casey, V. Developing trust in virtual software development teams. J. Theor. Appl. Electron. Commer. Res. 5 (August 2010), 41-58.
11. Cataldo, M., Mockus, A., Roberts, J. A., and Herbsleb, J. D. Software Dependencies, Work Dependencies, and Their Impact on Failures. IEEE TSE 35, 6 (2009).
12. Cataldo, M., Wagstrom, P. A., Herbsleb, J. D., and Carley, K. M. Identification of Coordination Requirements: Implications for the Design of Collaboration and Awareness Tools. Proc. CSCW '06, 353-362.
13. Conway, M. E. How Do Committees Invent? Datamation 14, 4 (1968), 28-31.
14. Curtis, B., Krasner, H., and Iscoe, N. A Field Study of the Software Design Process for Large Systems. Comm. ACM 31, 11 (1988), 1268-1287.
15. Damian, D., Kwan, I., and Marczak, S. Collaborative Software Engieneering. Computer Science Editorial Series. Springer-Verlag, May 2010, ch. Requirements-Driven Collaboration: Leveraging the Invisible Relationships between Requirements and People.
16. de Souza, C. R., Quirk, S., Trainer, E., and Redmiles, D. F. Supporting collaborative software development through the visualization of socio-technical dependencies. Proc. GROUP '07, 147-156.
17. de Souza, C. R., and Redmiles, D. F. The Awareness Network, To Whom Should I Display My Actions? And, Whose Actions Should I Monitor? IEEE TSE 37 (2011), 325-340.
18. de Souza, C. R. B., and Redmiles, D. An Empirical Study of Software Developers' Management of Dependencies and Changes. Proc. ICSE '08.
19. de Souza, C. R. B., Redmiles, D., Cheng, L.-T., Millen, D., and Patterson, J. How a good software practice thwarts collaboration: the multiple roles of apis in software development. Proc. FSE '04, 221-230.
20. DiMicco, J., Millen, D. R., Geyer, W., Dugan, C., Brownholtz, B., and Muller, M. Motivations for social networking at work. Proc. CSCW '08, 711.
21. Dougherty, D. Interpretive barriers to successful product innovation in large firms. Organization Science 3, 2 (1992), 179-202.
22. Fritz, T. Determining Relevancy: How Software Developers Determine Relevant Information in Feeds. Proc. CHI '11.
23. Fritz, T., and Murphy, G. C. Using information fragments to answer the questions developers ask. Proc. ICSE '10, 175-184.
24. Github, I. Github social coding, 2011. Available at: http://www.github. com.
25. Grudin, J. Groupware and social dynamics: eight challenges for developers. Comm. ACM 37 (January 1994), 92-105.
26. Gutwin, C., Greenberg, S., and Roseman, M. Workspace awareness in real-time distributed groupware: Framework, widgets, and evaluation. Proc. HCI on People and Computers XI '96, 281-298.
27. Guzzi, A., Pinzger, M., and van Deursen, A. Combining micro-blogging and ide interactions to support developers in their quests. ICSM, Early Research Achievements Track (2010), 1-5.
28. Halverson, C. A., Ellis, J. B., Danis, C., and Kellogg, W. A. Designing task visualizations to support the coordination of work in software development. Proc. CSCW '06, 39-48.
29. Hattori, L., and Lanza, M. Syde : A Tool for Collaborative Software Development. Proc. ICSE '08, 235-238.
30. Herbsleb, J. D., and Grinter, R. E. Splitting the Organization and Integrating the Code: Conway's Law Revisited. Proc. ICSE '99, 85-95.
31. Hinds, P., and McGrath, C. Structures that work: social structure, work structure and coordination ease in geographically distributed teams. Proc. CSCW '06, 343-352.
32. Holmes, R., and Walker, R. J. Customized awareness: recommending relevant external change events. Proc. ICSE '10, 465-474.
33. Jiang, H., and Carroll, J. M. Social capital, social network and identity bonds: a reconceptualization. Proc. C&T '09, 51-60.
34. Kraut, R. E., and Streeter, L. A. Coordination in Software Development. Comm. ACM 38, 3 (1995), 69-81.
35. Kwan, I., Schroter, A., and Damian, D. Does socio-technical congruence have an effect on software build success? a study of coordination in a software project. IEEE TSE 37 (May 2011), 307-324.
36. LaToza, T. D., Venolia, G., and DeLine, R. Maintaining mental models: a study of developer work habits. Proc. ICSE '06, 492-501.
37. Lim, S., Quercia, D., and Finkelstein, A. StakeNet: using social networks to analyse the stakeholders of large-scale software projects. Proc. ICSE '10, 295-304.
38. Maalej, W., and Happel, H.-J. From work to word: How do software developers describe their work? Proc. MSR '09, 121-130.
39. Mockus, A., Fielding, R. T., and Herbsleb, J. D. Two case studies of open source software development: Apache and mozilla. ACM TOSEM 11, 3 (2002), 309-346.
40. Mockus, A., and Herbsleb, J. D. Expertise browser: a quantitative approach to identifying expertise. Proc. ICSE '02, 503-512.
41. Omoronyia, I., Ferguson, J., Roper, M., and Wood, M. Using developer activity data to enhance awareness during collaborative software development. Journal of CSCW 18 (2009), 509-558.
42. Poile, C. Asymmetric dependence and its effect on helping behaviour in work groups. PhD thesis, University of Waterloo, 2010.
43. Rigby, P. C., and Storey, M.-A. Understanding broadcast based peer review on open source software projects. Proc. ICSE'11, 541-550.
44. Safayeni, F., Duimering, P. R., Zheng, K., Derbentseva, N., Poile, C., and Ran, B. Requirements engineering in new product development. Comm. ACM 51 (March 2008), 77-82. (Pubitemid 351357119)
45. Sarma, A., Noroozi, Z., and van der Hoek, A. Palantír: raising awareness among configuration management workspaces. Proc. ICSE '03, 444-454.
46. Sarma, A., Redmiles, D., and van der Hoek, A. Categorizing the spectrum of coordination technology. IEEE Computer 43 (2010), 61-67.
47. Sinha, V. S., Mani, S., and Sinha, S. Entering the circle of trust: developer initiation as committers in open-source projects. Proc. MSR '11, 133-142.
48. Sodan, A. C. How much do technical scientists really cooperate? ACM SIGCAS 36, 2 (June 2006).
49. Teasley, S. D., Covi, L. A., Krishnan, M. S., and Olson, J. S. Rapid Software Development through Team Collocation. IEEE TSE 28, 7 (2002), 671-683.
50. Treude, C., and Storey, M.-A. How Tagging Helps Bridge the Gap Between Social and Technical Aspects in Software Development. Proc. ICSE '09.
51. Wolf, T., Schroter, A., Damian, D., and Nguyen, T. Predicting build failures using social network analysis on developer communication. Proc. ICSE '09, 1-11.
52. Wu, A., DiMicco, J. M., and Millen, D. R. Detecting professional versus personal closeness using an enterprise social network site. Proc. CHI '10.
53. Xiang, P. F., Ying, A. T. T., Cheng, P., Dang, Y. B., Ehrlich, K., Helander, M. E., Matchen, P. M., Empere, A., Tarr, P. L., Williams, C., and Yang, S. X. Ensemble: a recommendation tool for promoting communication in software teams. Proc. RSSE '08, 2:1-2:1.