Persuading developers to buy into software process improvement: a local opinion and empirical evidence

This material is presented to ensure timely dissemination of scholarly and technical work. Copyright and all rights therein are retained by authors or by other copyright holders. All persons copying this information are expected to adhere to the terms and constraints invoked by each author's copyright. In most cases, these works may not be reposted without the explicit permission of the copyright holder.---- Copyright IEEE. Personal use of this material is permitted. However, permission to reprint/republish this material for advertising or promotional purposes or for creating new collective works for resale or redistribution to servers or lists, or to reuse any copyrighted component of this work in other works must be obtained from the IEEE.In order to investigate practitioners’ opinions of software process and software process improvement, we have collected a large volume of qualitative evidence from 13 companies. At the same time, other researchers have reported investigations of practitioners, and we are interested in how their reports may relate to our evidence. Thus, other research publications can also be treated as a form of qualitative data. In this paper, we review advice on a method, content analysis, that is used to analyse qualitative data. We use content analysis to describe and analyse discussions on software process and software process improvement. We report preliminary findings from an analysis of both the focus group evidence and four publications

An empirical evaluation of client-vendor relationships in high maturity Indian software outsourcing companies

The study presented in this thesis investigates offshore software outsourcing relationships. Offshore software outsourcing has been increasing continuously for the last decade. More and more software vendor companies from different countries such as India, Russia, Brazil and China are joining the offshore `bandwagon'. Indian software companies especially have managed to secure a leading position as offshore software outsourcing vendors. However, with more client companies outsourcing their software operations offshore, issues associated with the establishment and management of offshore outsourcing relationships have become more important. With the growing volume of offshore outsourcing, the number of failures is also increasing. A review of the literature suggests that success or failure is mainly dependent on the management of relationships between client and vendor. Subsequently, it is imperative to identify critical factors that can help to better manage offshore software outsourcing relationships. Furthermore, it is also important to identify the difficulties faced in managing offshore relationships and also how clients and vendors develop mutual trust. Trust is important to understand in the offshore software outsourcing context as it has been reported as the most significant contributor to the management of any human relationship. Nonetheless, different advantages that motivate clients to outsource are also important in understanding offshore software outsourcing. In this study, motivators, difficulties, critical relationship management factors and trust building factors are studied by means of empirical investigation into eighteen high maturity Indian software companies and six of their clients based in the USA and Europe. Multiple case studies with grounded theory analysis techniques are used to conduct the empirical investigation. Grounded theory, which is a part of qualitative research, helps to develop emergent model from empirical data. Furthermore, multiple case studies are used as objects to collect qualitative data and organise overall investigation. The research methods used were piloted with two Indian software companies before conducting the full empirical investigation. The results of this investigation suggest that client companies are motivated to outsource their software offshore by cost savings, quality, flexibility, core competence, skills availability, higher productivity, faster development, technical expertise and high maturity of vendor. The results also uncovered difficulties faced by clients and vendors in managing relationships. Difficulties include managing cultural differences, expectation mismatch, language differences, loss of control, distance, time zone differences, workforce reshuffling and post-contractual matters. This investigation further identifies critical factors to managing offshore outsourcing relationships such as effective communication, a process driven approach, commitment to the project, transparency in actions, consistency in performance, value addition and allocating resources effectively in the project. Furthermore, results from this study suggest that previous work reference, experience and reputation in the offshore outsourcing business, background of the key vendor employees, investments, prototyping and personal visits from the client are important for achieving trust. This study also identifies that to maintain trust in the relationship both clients and vendors perceive critical factors such as commitment, process driven approach, communication, confidentiality, performance, honesty, transparency, demonstrability, personal relationships and working together in outsourcing project. Based on the results of the empirical results and their discussions, this study presents an emergent model and practical guidelines for managing offshore software outsourcing relationships. The uniqueness of this investigation is in its large scale empirical investigation into high maturity software companies. Furthermore, most previous studies have investigated either clients or vendors, whereas this study investigates vendors and their corresponding clients. An investigation into trust in offshore software outsourcing relationships is also a significant addition to the existing literature relevant to software outsourcing. The empirical investigation gave rise to proposals for discussions and to an emergent empirical model. Thus the current body of knowledge in offshore software outsourcing is enhanced by this work. Moreover, practical guidelines, based on empirical results are proposed for client and vendors to help them manage their offshore software outsourcing relationships

Models of motivation in software engineering

Motivation in software engineering is recognized as a key success factor for software projects, but although there are many papers written about motivation in software engineering, the field lacks a comprehensive overview of the area. In particular, several models of motivation have been proposed, but they either rely heavily on one particular model (the job characteristics model), or are quite disparate and difficult to combine. Using the results from our previous systematic literature review (SLR), we constructed a new model of motivation in software engineering. We then compared this new model with existing models and refined it based on this comparison. This paper summarises the SLR results, presents the important existing models found in the literature and explains the development of our new model of motivation in software engineering

Knowledge Contribution Motivators – An Expectation-Confirmation Approach

Individual knowledge needs to be shared across IS developing organizations to provide information for all types of decisions. Considering knowledge management (KM) as a two-part process of knowledge contribution and knowledge seeking, we focus on the former one as it is (1) the required condition for knowledge sharing and (2) the greater challenge to accomplish by organizations compared to implementing successful knowledge seeking. Distinguishing different types of individual and organizational extrinsic motivators based on self-determination theory, we use expectation-confirmation theory (ECT) to analyze the extent to which software developers’ expectations towards knowledge contributions are fulfilled by organizations. Additionally, showing extrinsic motivators’ importance for software developers to contribute to KM systems, we provide organizations a roadmap for setting favorable conditions. Whereas our consolidation of previous research on knowledge contribution provides guidelines for future research on extrinsic motivators, we contribute to existing theory by applying ECT to the context of KM contribution

Police Knowledge Exchange: Full Report 2018

[Executive Summary] This report was commissioned to explore the enablers and barriers to sharing within and between police forces and between police forces and partners, including the public. This was completed from an interdisciplinary review of international literature covering sharing, knowledge exchange, learning and organisational learning. The literature broke down into four main factors; who, why, what and how. An introduction to the literature is presented with ‘Who’ is sharing which considers both personal identity and different institutional issues. The ‘Why’ literature covers issues of cultural and community motivators and barriers. The ‘What’ segment reviews concepts of data, information and knowledge and related legislative issues. Finally, the ‘how’ section spans face to face sharing approaches to technologies that produce both enablers and barriers. A series of 42 in-depth interviews and focus groups were completed and combined with 47 survey responses . The aim of the interviews, focus groups and survey was to show perceptions and beliefs around knowledge sharing from a small sample across policing in order to complement the findings from the literature review. The survey was adapted from a standardised questionnaire (Biggs, 1987). The Biggs questionnaire focused on what motivated students to learn and how they approached their learning. Our adapted survey looked at what motivated police to share, and how they approached sharing. The responses showed a trend, across the police, towards a motivation for sharing to develop a deeper understanding of issues. However, the approaches and the strategies they used to share with others, which were primarily driven by achieving and surface approaches (to get promoted and get the job done). According to Biggs (1987) this could leave them discontented as they never progress to a deeper understanding of issues. Scaffolding sharing within the police through processes that are clearly defined, effective and valued could help to overcome these issues. Within the interviews and focus group findings a similar structured approach to sharing was adopted. Within the ‘who’ section some key aspects around personal relationships, reciprocity and reputation were identified. The ‘why’ the police share was one of the largest discussion points. Not only was there a deep motivation to solve key policing issues there was an approach of reciprocity. Police sharing was deeply motivated to support ‘good practice’ in the prevention and detection of crime. However, a sharing barrier was identified in the parity of value given to different types of knowledge for example between professional judgement and research evidence knowledge. Sharing was achieved when there were reciprocal benefits, in particular with personal networks or face to face sharing which was noted as ‘safe’. Again, this was inhibited by misunderstandings around the ‘risks’ of sharing, frequently attributed to data protection legislation; producing cautious reactions and as an avoidance tactic to save time and effort sharing. However, a divide was noted between technical users and those who avoided any online systems for sharing; often due to poorly designed systems and a lack of confidence in how to use systems. The police culture was identified as being risk-adverse, and competitive due to multiple factors, a lack of supported time to share, Her Majesty’s Inspectorate of Constabulary (HMIC) reviews and promotion criteria. The result was perceived to be a poor cultural ability to learn from mistakes and a likelihood to repeat errors. A set of strategic recommendations are given and include the use of a sharing authorised professional practice for HMIC reviews, sharing networks and training. A further set of operational recommendations are given such as; sharing impact cases for evidence based practice, data sharing officers and evaluating mechanisms for sharing. This full report is supported by the Police Knowledge Exchange Summary Report 2018 which gives an overview of the findings and recommendations

Multi-factor motivation model in software engineering environments

In software engineering environments, motivation has become an imperative tool for increasing the productivity and creativity levels of projects. The aim of this research is to develop a validated conceptual multifactor and motivating model that represents the interaction between the organisational, occupational and interpersonal factors in software engineering environments. However, the application of well-known motivation tools cannot guarantee high motivational levels among the members of software engineering teams. Therefore, several phenomena have been monitored and empirically tested related to the daily practices in the software engineering industry. Reviewing the literature on motivation in software engineering uncovered a list of influential factors that could motivate individuals in the workplace. These factors have been suggested as being grouped into three categories (interpersonal, occupational and organisational). The literature review stage was followed by a preliminary study to discuss and validate these factors in greater detail by interviewing eight experts drawn from the software engineering industry. The preliminary study provided this research with an initial conceptual model that could broaden the understanding of the recent state of motivation in software engineering environments. The initial model was validated and expanded by conducting two types of research (quantitative and qualitative) based on the type of information gleaned. Accordingly, 208 experienced software engineers and members of teams in the software development industry were involved in this research. The results from this research revealed a statistically significant interaction between factors from different categories (interpersonal, occupational and organisational). This interaction has helped in developing an updated new model of motivation in software engineering. In addition, the application of motivation theories in software engineering could be affected by some work-related factors. These factors were found in this research to be member role, contract types, age, organisational structure and citizenship status. Thus, all these factors have been given a high consideration when designing rewards systems in software engineering

“Best Practice” without Evidence – Agile Software Methodology as Example

Despite the essentiality of education, and the widely known unscientific nature of expert opinion, education in general appears to be based on expert opinion. The example analyzed herein is of Agile software methodology, which is deemed a best practice and therefore taught in most IT studies, in Norway and most probably internationally. This is despite that it appears to be a well known fact within its respective field that the Agile methodology lacks scientific justification. A tertiary analysis was conducted to test this well known fact and to serve as basis for exploring what should be considered sufficient evidence for inclusion within official education. The result of the tertiary study is that, indeed, the evidence for the Agile methodology is scarce at best. A method to avoid such mistake is suggested, which could be valuable to science in general. This method entails employing philosophers of science, epistemologists, to counteract potential expert biases and verify the curriculum before it is accepted in official education

Motivation and Satisfaction of Software Engineers

Context: The proper management of people can help software organisations to achieve higher levels of success. However, the limited attention paid to the appropriate use of theories to underpin the research in this area leaves it unclear how to deal with human aspects of software engineers, such as motivation and satisfaction. Objectives: This article aims to expose what drives the motivation and satisfaction of software engineers at work. Methods: A multiple case study was conducted at four software organisations in Brazil. For 11 months, data was collected using semi-structured interviews, diary studies, and document analyses. Results: The Theory of Motivation and Satisfaction of Software Engineers (TMS-SE), presented in this article, combines elements from well established theories with new findings, and translates them into the software engineering context. Conclusion: The TMS-SE advances the understanding of people management in the software engineering field and presents a strong conceptual framework for future investigations in this area

Persuading developers to buy into software process improvement: an exploratory analysis

In order to investigate practitioners' opinions of software process and software process improvement, we have collected information from 13 companies, in a variety of ways i.e. the use of Repertory Grid Technique, survey and focus group discussions. Both the Repertory Grid Technique and the focus group discussions (43 discussions occurred, in total) produced a large volume of qualitative data. At the same time, other researchers have reported--investigations of practitioners, and we are interested in how their reports may relate to our own. Thus, other research publications can also be treated as a form of qualitative data. In this paper, we review advice on a method, content analysis, that is used to analyse qualitative data. Content analysis is a method for identifying and classifying words and phrases used in--ordinary language. We use content analysis to describe and analyse discussions on software--process and software process improvement. We report preliminary findings from an analysis--of both the focus group evidence and some publications. Our main finding is that there is an--apparent contradiction between developers saying that they want evidence for software process improvement, and what developers will accept as evidence. This presents a serious problem for research: even if researchers could demonstrate a strong, reliable relationship between software process improvement and improved organisational performance, there would still be the problem of convincing practitioners that the evidence applies to their particular situation