Investigating the impact of personality types on communication and collaboration-viability in pair programming - An empirical study

Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)

Volumn 4044 LNCS, Issue , 2006, Pages 43-52

  Sfetsos, Panagiotis ^a   Stamelos, Ioannis ^a   Angelis, Lefteris ^a   Deligiannis, Ignatios ^b  

^a ARISTOTLE UNIVERSITY OF THESSALONIKI   (Greece)

^b ALEXANDER TECHNOLOGICAL EDUCATIONAL INSTITUTE OF THESSALONIKI   (Greece)

Author keywords

[No Author keywords available]

Indexed keywords

COMMUNICATION SYSTEMS; CUSTOMER SATISFACTION; KNOWLEDGE ACQUISITION; NAVIGATION SYSTEMS; PROFESSIONAL ASPECTS; SOFTWARE ENGINEERING;

CONTROLLED EXPERIMENTS; MANDATORY PREFERENCE; NUISANCE RATIO; PAIR PROGRAMMING;

COMPUTER PROGRAMMING;

EID: 33746192574     PISSN: 03029743     EISSN: 16113349     Source Type: Book Series    
DOI: 10.1007/11774129_5     Document Type: Conference Paper

References (18)

1. Basili V. and Weiss D. A Methodology for Collecting Valid Software Engineering Data. IEEE Transactions on software engineering, vol SE-10, pp. 728-738; Nov. 1984.
2. Basili V. and Rombach H. The TAME Project: Towards Improvement- Oriented Software Environments; IEEE Transactions on software engineering, 14(6); 758-773; June 1988.
3. Beck, K. Extreme Programming Explained: Embrace Change. Reading, Massachusetts: Addison-Wesley. 2000.
4. Briand, L., Differding, C., Rombach, H. Practical Guidelines For Measurement-Based Process Improvement, Software Process Improvement and Practice, 2(4), pp253-280, 1996.
5. Briand L., Arisholm S., Counsell F., Houdek F. and Thevenod-Fosse P. Empirical Studies of Object-Oriented Artifacts, Methods, and Processes: State of the Ar and Future Directions. Empirical Software Engineering, 2000.
6. Cockburn, A. The Coffee Machine Design Problem: Part 1 & 2. C/C++ User's Journal, May/June, 1998.
7. Cockburn, A. Agle Software Development. Addison-Wesley, 2002.
8. Dutoit, A. and Bruegge B. Communication Metrics for Software Development. IEEE transactions on Software Engineering, 1998.
9. Fenton, N. Software Metrics, A Rigorous Approach. Chapman & Hall, 1991.
10. Highsmith, J. Agle Software Development Ecosystems, Addison Wesley, 2002.
11. Katira, N., Williams, L., Wiebe, E., Miller, C., Balik, S., Gehringer, E. On Under-standing Compatibility of Student Pair Programmers. SIGCSE'04, 3-7, 2004.
12. Keirsey, D., and Bates, M., Please Understand Me, Del Mar, California: Prometheus Book Company, 1984.
13. Myers, Isabel, "Manual: The Myers-Briggs Type Indicator," Palo Alto, California: Consulting Psychologists Press, 1975.
14. Saeki, M. Communication, Collaboration, and Cooperation in Software Development - How Should We Support Group Work in Software Development? Proc. Asia-Pacific Soft-ware Eng. Conf. Brisbane, Australia, 1995.
15. Seaman, C., and Basili, V. "An Empirical Study of Communication in Code Inspections," Proc. 19th Int'l Conf. Software Eng., Boston, May 1997.
16. Sfetsos, P., Angelis, L., Stamelos, I. "Investigating The Extreme Programming System- An Empirical Study". Empirical Software Engineering, Vol 11, Nbr. 2, pp. 269-301, June 2006 (to appear).
17. Sundstrom, E., De Meuse, K., and Futrell, D. Work Teams, AmericanPsychologist, February, 1990, pp. 120-133.
18. Wohlin C., Runeson P., Host M., Ohlson M., Regnell B. and Wesslén A. Experimentation in Software Engineering: An Introduction, Kluwer Academic Publishers, 2000.