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

Motivators and de-motivators in software process improvement : an empirical study

Software quality problems are a concern for the software engineering community. Software Process Improvement (SPI) is the most recent and most popular approach adopted to address this problem. SPI focuses on the processes that develop software in order to deliver improvements to the product. Despite this popularity of SPI there is insufficient evidence of its successful impact on software quality. Quality problems in software continue. This has led to some concern in the industry about the effectiveness of SPI in tackling the problem of software quality. There is evidence to suggest that SPI does improve software quality. However, there is also evidence to suggest that SPI is not sufficiently supported by software practitioners. This lack of support may be one of the reasons why SPI appears to be failing at tackling the problem of software quality. In this research it is argued that this lack of support for SPI is caused by companies' inability to manage software practitioners' motivation for SPI properly. Companies may not be managing software practitioners' motivation for SPI properly because they may not understand them. There is therefore a need to better understand what software practitioners'motivations for supporting SPI are. A review of the literature suggests a set of guidelines that can improve software practitioners' support for SPI. The literature also suggests four themes that underpin software practitioners' motivation for SPI. The four themes are SPI managers' perception of the motivators and demotivators for SPI, software practitioners' motivators, software practitioners' de-motivators and the differences in software practitioners' motivators and de-motivators. The basis of this research is that exploring the four themes that underpin software practitioners' motivation for SPI improves understanding of the factors that influence support for SPI. This knowledge of the factors that influence support for SPI can then be used to validate and provide an empirical basis for the literature-suggested guidelines. Thereby improving confidence in the "-IL iidelines. The four themes underpinning software practitioners' motivation for SPI are examined through empirical studies. Findings from these studies suggest that SPI managers perceive senior managers as not supportive of SPI. They also perceive developers as not enthusiastic about SPI. The findings also suggest that the key motivators of software practitioners for SPI are visible support and commitment from senior management and empowerment of practitioners, whereas the key de-motivators are related to constraints on resources and a failure to secure practitioners' buy-in for SPI. There are also differences in what motivates and de-motivates different practitioner groups for SPI and these differences are related to the jobs that practitioners do. Finally, software practitioners have different perceptions of their role in SPI, which are related to their software development roles. This suggests that the objectives of SPI should be tailored to the software development objectives of practitioners in order to improve their support for SPI. Overall, findinas from these studies confirm most of the guidelines suggested by the t:, literature. The confirmed guidelines are offered as insight to improving support for SPI, which can in turn help to improve the impact of SPI on software quality

Mapeamento da Literatura sobre Fatores Humanos e Resistência em Melhoria de Processos de Software: Protocolo e Extração de Dados

Contexto: Iniciativas de melhoria de processos de software bem-sucedidas lidam com muitos desafios, incluindo a compreensão dos fatores críticos de sucesso que podem ajudar ou dificultar os esforços a serem feitos. Motivação: Embora os fatores huma-nos compreendam uma categoria importante de fatores críticos de sucesso, seus efei-tos nas iniciativas de melhoria de processos de software não são totalmente claros. Objetivo: Nosso objetivo é identificar e entender como os fatores humanos, especial-mente a resistência, afetam as iniciativas de melhoria de processos de software. Mé-todo: Um mapeamento sistemático da literatura foi realizado em quatro bancos de dados científicos, considerando artigos publicados até 2018. Resultados: Foram iden-tificados 30 artigos que responderam às perguntas da pesquisa, apontando 29 fato-res humanos que influenciam as iniciativas de melhoria de processos de software. Cinco dos 29 fatores humanos foram considerados os mais críticos: Apoio da Alta Gerência, Envolvimento dos Membros da Organização, Experiência da Equipe, Com-prometimento dos Membros da Organização e Habilidades e Competências Técni-cas/Conhecimento. Conclusão: Várias relações de efeito foram encontradas entre fa-tores humanos e fatores críticos de sucesso. Tais relacionamentos mostram quão complexa é a influência desses fatores humanos nas iniciativas de melhoria de pro-cessos de software. Oferecemos essas descobertas que podem sensibilizar profissio-nais de software e especialistas em iniciativas de melhoria de processos de software, sobre os impactos e dificuldades que fatores humanos podem gerar a tais iniciativas

A requirements-based software process maturity model

The requirements phase of software development is an on-going problem for the software engineering community. The many disparate recommendations and best practices found in the literature make it difficult for software organisations to recognise which practices apply to their individual needs. The aim of this thesis is to pull together key solutions into a framework that allows practitioners to assess where their requirements process needs strengthening and to provide a means in which improvements can be achieved. In this thesis I show how I design, develop and validate a model of requirements engineering processes. This requirements capability maturity model (R-CMM) adheres to the characteristics of the Software Engineering Institute's Software Capability Maturity Model (SW-CMM) and is designed to take practitioners from an immature process capability through to an advanced capability. I contribute to the body of knowledge in both software process improvement and requirements engineering (RE) by providing rigorous detail of how a process maturity framework is developed to support RE practices. The model is generic and should apply to many software development organisations. The R-CMM guides users towards a view of RE that is based on goals and is problem driven. The SW-CMM framework is transformed into a simplified model that relates goals and problems to individual RE practises

Using Workshops to Improve Security in Software Development Teams

Though some software development teams are highly effective at delivering security, others either do not care or do not have access to security experts to teach them how. Unfortunately, these latter teams are still responsible for the security of the systems they build: systems that are ever more important to ever more people. Yet many, perhaps most, security problems can be prevented with careful design, construction and configuration of the software and systems involved, so software developers have a major contribution to make. This research investigated how to help teams of software developers achieve better security. An initial qualitative survey of 15 secure software development professionals highlighted a range of security assurance and motivation techniques suitable for teams of developers, and emphasised the human interaction aspects. A further quantitative survey of 330 successful Android developers then identified a baseline of current security practices in software development. Based on these surveys, the author created an intervention package to help software developers. Action Research techniques were used to trial and improve it in two one-year cycles with a total of 19 development teams in 11 different organisations. The later development of the package concentrated on empowering the developers involved, and reducing the involvement required from the researchers. By proving that a set of structured workshops can have an impact on the security performance of a team for a reasonable cost and without the support of security professionals, this research offers a powerful means to enhance development security in the UK, creating more secure software and systems for all users

An agile information flow consolidator for delivery of quality software projects: technological perspective from a South African start-up

In today’s knowledge-based economy, modern organisations understand the importance of technology in their quest to be considered global leaders. South African markets like others worldwide are regularly flooded with the latest technology trends which can complicate the acquisition, use, management and maintenance of software. To achieve a competitive edge, companies tend to leverage agile methods with the best possible combination of innovative supporting tools as a key differentiator. Software technology firms are in this light faced with determining how to leverage technology and efficient development processes for them to consistently deliver quality software projects and solutions to their customer base. Previous studies have discussed the importance of software development processes from a project management perspective. African academia has immensely contributed in terms of software development and project management research which has focused on modern frameworks, methodologies as well as project management techniques. While the current research continues with this tradition by presenting the pertinence of modern agile methodologies, it additionally further describes modern agile development processes tailored in a sub-Saharan context. The study also aims novelty by showing how innovative sometimes disruptive technology tools can contribute to producing African software solutions to African problems. To this end, the thesis contains an experimental case study where a web portal is prototyped to assist firms with the management of agile project management and engineering related activities. Literature review, semi-structure interviews as well as direct observations from the industry use case are used as data sources. Underpinned by an Activity Theory analytical framework, the qualitative data is analysed by leveraging content and thematic oriented techniques. This study aims to contribute to software engineering as well as the information systems body of knowledge in general. The research hence ambitions to propose a practical framework to promote the delivery of quality software projects and products. For this thesis, such a framework was designed around an information system which helps organizations better manage agile project management and engineering related activities.Information SciencePh. D. (Information Systems

Investigating software process in practice: a grounded theory perspective

This thesis is concerned with how software process and software process improvement is practiced within the indigenous Irish software product industry. Using the grounded theory methodology, the study utilises in-depth interviews to examine the attitude and perceptions of practitioners towards software process and software process improvement. The outcome of the work is a theory, grounded in the field data, that explains how software processes are formed and evolve, and when and why software process improvement is undertaken. The resultant grounded theory is based on two conceptual themes, Process Formation and Process Evolution, and one core theoretical category, Cost of Process. The empirical investigation shows that software process improvement programmes are implemented by companies as a reaction to business events, and how many software managers reject software process improvement because o f the associated costs. In addition, indigenous Irish software companies largely ignore commercial best practice software process improvement models, and the reasons for this are discussed. The research also argues that software process improvement is not solely technologycentred but is also affected by wider human and organisational factors. As these ‘sociocultural’ influences have been more widely addressed in the Information Systems discipline, than in Software Engineering, this work draws on the experiences and lessons from both disciplines and ultimately resides between these two academic fields. The results o f this work provide new light on the issues facing software process and process improvement in small software product companies and make a contribution towards bridging the gaps between research and practice, and theory and practice, in both Software Engineering and Information Systems