Information needs in collocated software development teams

Proceedings - International Conference on Software Engineering

Volumn , Issue , 2007, Pages 344-353

  Ko, Andrew J ^a   DeLine, Robert ^b   Venolia, Gina ^b  

^a Carnegie Mellon University

^b MICROSOFT RESEARCH   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

CODES (SYMBOLS); COMPUTER SYSTEMS PROGRAMMING; DATA ACQUISITION; KNOWLEDGE ACQUISITION;

ARTIFACTS; PROGRAM BEHAVIORS; PROGRAM STATES;

SOFTWARE DESIGN;

EID: 34548742277     PISSN: 02705257     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/ICSE.2007.45     Document Type: Conference Paper

References (20)

1. Biehl, J.T., Czerwinski, M., Smith, G., Robertson, G.G., Bailey, B. (2007). FASTDash: A Visual Dashboard for Fostering Awareness in Software Teams. To appear at CHI 2007.
2. Brooks, F.P. Jr. (1975). The Mythical Man-Month: Essays on Software Engineering. Addison Wesley, Reading, MA.
3. Cataldo, M., P. Wagstrom, J.D. Herbsleb, K. Carley (2006). Identification of Coordination Requirements: Implications for the Design of Collaboration and Awareness Tools. Computer Supported Cooperative Work 2006, Banff, Alberta, 353-362.
4. Chong, J., Rosanne Siino. Interruptions on Software Teams: A Comparison of Paired and Solo Programmers. Computer Supported Cooperative Work2006, Banff, Alberta, p.28-39.
5. de Souza, C.R.B., D.F. Redmiles, G. Mark, J. Penix, M. Sierhuis (2003) Management of Interdependencies in Collaborative Software Development: A Field Study. ISESE, Rome, Italy, 294-303.
6. Eisenstadt, M. (1997). "My Hairiest Bug" War Stories. CACM, 40(4), 30-37.
7. Gonzalez, V., G. Mark., J. Harris (2005). No Task Left Behind? Examining the Nature of Fragmented Work. CHI, Portland, OR, 321-330.
8. Gutwin, C., R. Penner, K. Schneider, K. (2004). Group Awareness in Distributed Software Development. CSCW, Chicago, IL, 72-81.
9. Hertzum, M. (2002). The Importance of Trust in Software Engineers' Assessment of Choice of Information Sources. Information and Organization, 12(1), 1-18.
10. Ko, A.J., B.A. Myers, H.H. Aung (2004). Six Learning Barriers in End-User Programming Systems. VL/HCC, Rome, Italy, 199-206.
11. Ko, A.J., B.A. Myers, M.J. Coblenz, H.H. Aung (2006). An Exploratory Study of How Developers Seek, Relate, and Collect Relevant Information during Software Maintenance Tasks. TSE, 971-987.
12. McDonald, D.W., M.S. Ackerman (1998). Just Talk to Me: A Field Study of Expertise Location. CSCW, Seattle, WA, 315-324.
13. LaToza, T.D., G. Venolia, R. DeLine. (2006). Maintaining Mental Models: A Study of Developer Work Habits. ICSE, Shanghai, China, 492-501.
14. Perlow, L.A. (1999). The Time Famine: Toward a Sociology of Work Time. Administrative Science Quarterly, 44(1), 57-81.
15. Perry, D.E., N.A. Staudenmayer, L.G. Votta (1994). People, Organizations and Process Improvement. IEEE Software, July, 36-45.
16. Sandusky, R.J., L. Gasser (2005). Negotiation and Coordination of Information and Activity in Distributed Software Problem Management. GROUP, Sanibel Island, FL, 187-196.
17. Sarma, A., Z. Noroozi, A. van der Hoek, Palantír: Raising Awareness among Configuration Management Workspaces. ICSE, 2003, Portland, OR, 444-454.
18. Seaman, C.B., V.R. Basili (1998). Communication and Organization: An Empirical Study of Discussion in Inspection Meetings. TSE. 24(7), 559-572.
19. Sridharan, M., S.J. Fink, R. Bodik. Thin Slicing. To appear at PLDI 2007.
20. Sillito, J., G. Murphy, K. De Volder (2006). Questions Programmers Ask During Software Evolution Tasks. SIGSOFT/FSE, Portland, OR, 23-34.