Who should work with whom?: building effective software project teams
TL;DR: Personality type analysis can help take the guesswork out of putting together a high-performance software project team.
Abstract: Personality type analysis can help take the guesswork out of putting together a high-performance software project team.
Citations
More filters
TL;DR: In this paper, a conceptual model, which draws on the technology acceptance model and resource-based theory, is developed and tested using quantitative data from B2B organizations in the UK.
259 citations
TL;DR: There are knowledge gaps in the research area of behavioral software engineering and that earlier research has been focused on a few concepts, which have been applied to a limited number of software engineering areas, according to the result.
230 citations
TL;DR: The landscape of current published empirical and theoretical studies that deal with the role of personality in software engineering is plotted to plot, and contradictory evidence was found that might have been caused by differences in context, research method, and versions of the tests used in the studies.
186 citations
TL;DR: This study explores how team leaders sense the need for technology adaptation intervention in distributed, computer-mediated ("virtual") teams and produces a five-trigger model that provides a diagnostic tool for examining real, multi-trigger team technology adaptation contexts, enabling better leader training and evaluation.
Abstract: This study explores how team leaders sense the need for technology adaptation intervention in distributed, computer-mediated ("virtual") teams. Analysis and coding of critical incident data collected in interviews of practicing leaders produce a five-trigger model including (1) external constraint, (2) internal constraint, (3) information and communication technology (ICT) inadequacy, (4) ICT knowledge, skills, and abilities inadequacy, and (5) trust and relationship inadequacies. The resulting five-trigger model provides several key contributions including (1) a diagnostic tool for examining real, multi-trigger team technology adaptation contexts, enabling better leader training and evaluation as well as improved research on team technology adaptation and interventions and (2) a better understanding of the relationship between the technology structure strength indicators in adaptive structuration theory and the need for team technology adaptation intervention.
125 citations
Cites background from "Who should work with whom?: buildin..."
...The sample for this study was purposeful in that we selected experienced managers currently engaged in IS projects in order to maximize information-rich cases....
[...]
TL;DR: There is important difference between the two groups of pairs, indicating better communication, pair performance and pair collaboration-viability for the pairs with heterogeneous personalities and temperaments.
Abstract: In this paper, pair programming is empirically investigated from the perspective of developer personalities and temperaments and how they affect pair effectiveness. A controlled experiment was conducted to investigate the impact of developer personalities and temperaments on communication, pair performance and pair viability-collaboration. The experiment involved 70 undergraduate students and the objective was to compare pairs of heterogeneous developer personalities and temperaments with pairs of homogeneous personalities and temperaments, in terms of pair effectiveness. Pair effectiveness is expressed in terms of pair performance, measured by communication, velocity, design correctness and passed acceptance tests, and pair collaboration-viability measured by developers' satisfaction, knowledge acquisition and participation. The results have shown that there is important difference between the two groups, indicating better communication, pair performance and pair collaboration-viability for the pairs with heterogeneous personalities and temperaments. In order to provide an objective assessment of the differences between the two groups of pairs, a number of statistical tests and stepwise Discriminant Analysis were used.
112 citations
Cites background or methods from "Who should work with whom?: buildin..."
...Type is one important component of the complex human personality.” However, personality/temperament type assessment has proven to be effective as a tool for understanding individual differences and improving relationships (Captez 2003; Ferdinandi 1998; Gorla and Lam 2004; McDonald and Edwards 2007)....
[...]
...However, personality/temperament type assessment has proven to be effective as a tool for understanding individual differences and improving relationships (Captez 2003; Ferdinandi 1998; Gorla and Lam 2004; McDonald and Edwards 2007)....
[...]
...Managers have much to gain from psychology to understand where and why slowdowns occur (Beck 2000; Cockburn 2002; Ferdinandi 1998; Gorla and Lam 2004)....
[...]
References
More filters
Book•
01 Jan 1982
TL;DR: Software Engineering A Practitioner's Approach recognizes the dramatic growth in the field of software engineering and emphasizes new and important methods and tools used in the industry.
Abstract: From the Publisher:
Well-suited for both the student and the working professional,Software Engineering A Practitioner's Approach recognizes the dramatic growth in the field of software engineering and emphasizes new and important methods and tools used in the industry.
8,224 citations
TL;DR: This study investigates the importance of expertise coordination through a cross-sectional investigation of 69 software development teams and reveals that expertise coordination shows a strong relationship with team performance that remains significant over and above team input characteristics, presence of expertise, and administrative coordination.
Abstract: Like all teams, knowledge teams must acquire and manage critical resources in order to accomplish their work. The most critical resource for knowledge teams is expertise, or specialized skills and knowledge, but the mere presence of expertise on a team is insufficient to produce high-quality work. Expertise must be managed and coordinated in order to leverage its potential. That is, teams must be able to manage their skill and knowledge interdependencies effectively through expertise coordination, which entails knowing where expertise is located, knowing where expertise is needed, and bringing needed expertise to bear. This study investigates the importance of expertise coordination through a cross-sectional investigation of 69 software development teams. The analysis reveals that expertise coordination shows a strong relationship with team performance that remains significant over and above team input characteristics, presence of expertise, and administrative coordination.
1,685 citations
TL;DR: Since its inception, the software industry has been in crisis and problems with software systems are common and highly-publicized occurrences.
Abstract: Since its inception, the software industry has been in crisis. As Blazer noted 20 years ago, “[Software] is unreliable, delivered late, unresponsive to change, inefficient, and expensive … and has been for the past 20 years” [4]. In a survey of software contractors and government contract officers, over half of the respondents believed that calendar overruns, cost overruns, code that required in-house modifications before being usable, and code that was difficult to modify were common problems in the software projects they supervised [22]. Even today, problems with software systems are common and highly-publicized occurrences.
1,121 citations
Book•
01 Mar 2004
1,055 citations