Fundamentals of software engineering
Fundamentals of software engineering
A social process model of user-analyst relationships
MIS Quarterly
The mythical man-month (anniversary ed.)
The mythical man-month (anniversary ed.)
The case for collaborative programming
Communications of the ACM
Extreme programming explained: embrace change
Extreme programming explained: embrace change
Information systems development: can there be “good” conflict?
SIGCPR '00 Proceedings of the 2000 ACM SIGCPR conference on Computer personnel research
Questioning Extreme Programming
Questioning Extreme Programming
Strengthening the Case for Pair Programming
IEEE Software
Managing conflict in software testing
Communications of the ACM - Multimodal interfaces that flex, adapt, and persist
Controlled experimentation on adaptations of pair programming
Information Technology and Management
Video analysis of pair programming
Proceedings of the 2008 international workshop on Scrutinizing agile practices or shoot-out at the agile corral
Developers and Moderators: Observations in the Co-development of an Online Social Space
IDGD '09 Proceedings of the 3rd International Conference on Internationalization, Design and Global Development: Held as Part of HCI International 2009
A model of job satisfaction for collaborative development processes
Journal of Systems and Software
Exploratory comparison of expert and novice pair programmers
CEE-SET'08 Proceedings of the Third IFIP TC 2 Central and East European conference on Software engineering techniques
Collaboration in software development: a spotlight
Proceedings of the CUBE International Information Technology Conference
Considering rigor and relevance when evaluating test driven development: A systematic review
Information and Software Technology
Hi-index | 0.00 |
Pair Programming is an innovative collaborative software development methodology. Anecdotal and empirical evidence suggests that this agile development method produces better quality software in reduced time with higher levels of developer satisfaction. To date, little explanation has been offered as to why these improved performance outcomes occur. In this qualitative study, we focus on how individual differences, and specifically task conflict, impact results of the collaborative software development process and related outcomes. We illustrate that low to moderate levels of task conflict actually enhance performance, while high levels mitigate otherwise anticipated positive results.