Personality characteristics in an XP team

Abstract

There is a "folk belief" that certain personalities fit with particular systems development roles: however, there is little evidence to confirm this supposition. As part of a larger study an XP development team was investigated using a repertory grid approach (this is discussed in detail) to determine whether coherent personalities and characteristics emerge for different roles. The results, which are inevitably limited, suggest that this is the case. Further work remains to be done to build a large corpus of data for future analysis before firm mappings can be made between appropriate personality characteristics and software development roles.

Comparación de efectividad de las técnicas de educción de requisitos software: visión novel y experta

“…Respecto al uso de emparrillado, existen algunos trabajos que han utilizado la técnica para comparar las características de los integrantes de equipos de desarrollos en XP [15] y para comparar las destrezas deseadas para los ingenieros de software [16]. Sin embargo, no hay trabajos que la usen para comparar técnicas del proceso de requisitos.…”

The repertory grid technique: Its place in empirical software engineering research

“…This method is appropriate if the researcher is interested in learning more about a specific set of elements, or if they want to make comparisons on people's response on a particular set of elements. A number of studies have taken this approach including [25,34].…”

“…In addition Stewart [31] argues that a combination of the two can lead to an improved understanding for the participant leading to enhanced constructs. We used this combination to study the personality characteristics that were associated with specific roles in an XP development team [34].…”

“…It is acknowledged that this is a time-efficient method of acquiring data, but it reduces the richness of the data that can be gathered, and also diminishes the researcher's confidence in the validity of the resultant data (and in the process having been understood and properly followed). These shortcomings were experienced in using such a fixed grid and administration process and were reported in full in [34,Chapter 7].…”

“…The repertory grid has as its elements the eight distinct studies that were being investigated by the researchers (thus in essence these elements were supplied). The elements are: risks in third party software development projects [21,22], practitioner roles in SPI [2], successful software inspection process [13], excellent systems analysts [14][15][16][17], characteristics in system development team members [34], generic team traits v. software team roles [33] , ISD training and impacts on cognitive structure [20], identifying aspects in requirements [23].…”