Pekka Abrahamsson

The interaction between organizational subcultures and user-centered design-a case study of an implementation effort

Usability is a quality characteristic of a software product or system. User-centered design (UCD) is an approach focusing on making systems usable. However, improving the position of UCD is widely recognized as a challenge. This paper reports results from a case study, in which a small software development company was introduced to UCD principles and activities, and thus expected to change their current practice. The paper takes a culture-oriented approach to the analysis. The focus is on the interaction between organizational culture and UCD, organizational culture being conceived as a set of subcultures. The results indicate that there exist differences: 1) in the views of the nature of UCD; 2) in the motives for implementing it; and 3) in the experiences gained and interpretations made of the use of it in relation to each subculture. The implications for the prospective research and practice are discussed.

Is management commitment a necessity after all in software process improvement

Literature and practice has established that the lack of management commitment has been one of the top reasons for a failed SPI (software process improvement) initiative. The paper reports results from an ongoing study aimed at clarifying the role and the meaning of management commitment in SPI initiatives. Results from five focused interviews with SPI professionals are reported together with results from 12 SPI initiatives where the level of management commitment (in terms of concrete signs) was measured in order to test whether it would correlate with the level of success of an SPI initiative. In contrast with the evidence from the literature, the results show that none of the signs of management commitment correlated significantly with the success of the SPI initiatives. It is suggested that the concept of champion may have explained the SPI project success better than management commitment. The paper concludes that many of the SPI initiatives do not require management commitment beyond obtaining the resources needed.

The personal software process: experiences from Denmark

The focus of the research and practice in software process improvement (SPI) is shifting from traditional large-scale assessment based improvement initiatives to smaller sized, tailored initiatives where the emphasis is on the development personnel and their personal abilities. Personal software process (PSP/sup SM/) is a method designed for improving the personal capabilities of the individual software engineer. This paper contributes to the body of knowledge within this area by reporting experiences from Denmark. The findings indicate an improvement in effort estimation skills and an increase in the resulting product quality in terms of reduced total defect density. The data shows that even with a relatively small effort (i.e., 10%) used in defect prevention activities (i.e., design and code reviews) almost one third of all defects could be removed and, consequently, the time required for the testing was reduced by 50%. On the basis of this data, the use of the PSP method in the software industry is discussed.

Modelling Usability Capability - Introducing the Dimensions

Usability capability is a characteristic of a development organization that predicts the level of usability the development projects are capable of achieving. Our experiments with the existing usability capability models indicate that current process assessment methods do not discover all relevant problems that might impede effective user-centered design (UCD) in development organizations. We propose an enhanced model where the usability capability is analyzed from three dimensions: user-centered infrastructure, implementation of user-centered practices in development projects, and business management commitment to usability as a competitive asset.

Commitment in software process improvement - in search of the process

Studies have shown that nearly two-thirds of all software process improvement (SPI) efforts have failed or at least fell short of expectations. Commitment has been argued to play an important role in determining the outcome of an SPI endeavor. This paper reports preliminary results from a study that attempts to explicate commitment process in SPI. Four SPI efforts were studied in two different organizations using action research approach. A new model to study the evolvement of commitment through commitment nets is introduced. Results indicate that commitment process is about the arrival, existence and departure of a concern and action in actors commitment net. Analysis and discussion of means used to transfer concerns at individual, group and organizational level is provided.

Commitment to Software Process Improvement—Development of Diagnostic Tool to Facilitate Improvement

This paper suggests that by operationalizing the concept of commitment in the shape of a model, a new insight is provided in improving software processes—a more human centered approach as opposed to various technical approaches available. In doing so the SPI managers/change agents are able to plan better the software process improvement initiative and benchmark successful projects (as well as failed ones). Results from five interviews with SPI professionals on the proposed Behavior-based Commitment Model are reported, together with early results from the empirical test in 14 software process improvement projects. Early results suggest that the behaviors introduced in the model are relevant in SPI initiatives, the use of model raises the awareness about the people issues in improving processes, and the model could be used aside with CMM, SPICE or other process improvement models.