Agile Software Process Improvement Research Articles

Business process management approach for improving agile software process and agile maturity

AbstractContinuous improvement of agile software processes is inevitable in order to reach sustainable and high‐quality project outcomes. In this sense, organizations need guidance on how to apply agile software process improvement effectively; comprehensive approaches with in‐depth analysis and guidelines are required to keep software processes in balance and to continuously improve them, as in a typical business process, over time. This research aims to explore the implementation of Business Process Management approach for improving an agile software process and accordingly agile maturity level. Many organizations utilize from Business Process Management approach in order to improve workflows and to discover organization‐specific weaknesses. For this purpose, the study presents a practical, flexible model based on Business Process Management approach for agile software process improvement, which also incorporates maturity assessment for measuring the agile maturity level. Furthermore, an exploratory case study with a triangulation methodology of mixed methods was carried out for implementation of the model. The research puts forward that Business Process Management approach can be used for in‐depth analysis of agile software process, discovery of problems, and redesign of the process. The research roadmap introduces worthwhile insights on agile software process improvement for researchers and practitioners.

How has SPI changed in times of agile development? Results from a multi‐method study

AbstractThe emergence of agile methods and practices has not only changed the development processes but might also have affected how companies conduct software process improvement (SPI). Through a set of complementary studies, we aim to understand how SPI has changed in times of agile software development. Specifically, we aim (a) to identify and characterize the set of publications that connect elements of agility to SPI, (b) to explore to which extent agile methods/practices have been used in the context of SPI, and (c) to understand whether the topics addressed in the literature are relevant and useful for industry professionals. To study these questions, we conducted an in‐depth analysis of the literature identified in a previous mapping study, an interview study, and an analysis of the responses given by industry professionals to SPI‐related questions stemming from an independently conducted survey study. Regarding the first question, we identified 55 publications that focus on both SPI and agility of which 48 present and discuss how agile methods/practices are used to steer SPI initiatives. Regarding the second question, we found that the two most frequently mentioned agile methods in the context of SPI are Scrum and Extreme Programming (XP), while the most frequently mentioned agile practices are integrate often, test‐first, daily meeting, pair programming, retrospective, on‐site customer, and product backlog. Regarding the third question, we found that a majority of the interviewed and surveyed industry professionals see SPI as a continuous activity. They agree with the agile SPI literature that agile methods/practices play an important role in SPI activities but that the importance given to specific agile methods/practices does not always coincide with the frequency with which these methods/practices are mentioned in the literature.

Agile software process improvement: a collaborative game toolbox

Software development organisations are interested in adopting new agile methods and techniques. However, they often do not have the time and resources to explore available approaches or to customise them to the current situation at the project or organisational levels. As software companies are usually dealing with significant pressure and have to demonstrate productivity, time for software process improvement (SPI) is very limited. Using serious collaborative games can be helpful for the deployment of certain best practices recommended by agile methods. With the objective of facilitating SPI in organisations, the authors propose a ready-to-use collaborative game toolbox that is oriented for practical use in project team meetings. The set of collaborative games included in the toolbox have been designed for agile teams, regardless of the maturity level, to innovate and improve communication and cohesion, and to bring business value out of agile ceremonies.

Lean and agile software process improvement in traditional and agile environments

AbstractThe culture of traditional organizations favors firmly established processes and standardization. Therefore, the adoption of Agile and Lean approaches in these organizations is a challenging issue. This paper presents an overview and outlook of the most well‐known Agile and Lean approaches in order to identify which kind of continuous software process improvement (SPI) is inherent in these approaches. The main objective of this research is to show that Lean and Agile SPI approaches can be pursued depending on the target environment, both in traditional and in agile organizations.

Empirical Research on Critical Success Factors of Agile Software Process Improvement

In this paper, we discuss agile software process improvement in P company with their description of process management in current level and analysis of problems, design the P Company success factors model in organizational culture, systems, products, customers, markets, leadership, technology and other key dimensions, which is verified through questionnaire in P company. In the end, we apply knowledge creation theory to analyze the open source software community with successful application of the typical agile software method, propose ten principles of knowledge creation in open source software community: Self-organizing, Code sharing, Adaptation, Usability, Sustention, Talent, Interaction, Collaboration, Happiness, and Democracy.

SPI agility: How to navigate improvement projects

AbstractIn this study, we argue that today's changing business environment calls for agile Software Process Improvement (SPI) practices. The study combines experiences from 18 SPI projects executed from 1998 to 2002 at Ericsson in Gothenburg with insights from SPI and agility theory. We suggest that agile SPI practices are both effective and flexible; they employ adaptive governance mechanisms at the corporate level; and they combine different tactics on the project level. We identify and compare two different tactics for SPI projects. Inspired by procedural thinking, the first tactic, the supertanker, employs process‐push and aims for efficient process development and diffusion. On the basis of adaptive thinking, the second tactic, the motorboat, facilitates practice‐pull and aims for adaptive process development and diffusion. We also discuss how agile SPI practices require understanding of the different types of waters in which the two tactics navigate effectively. Copyright © 2006 John Wiley & Sons, Ltd.

Improving software organizations: agility challenges and implications

PurposeThe paper seeks to explore the impact of events in Software Process Improvement (SPI) environments based on a longitudinal study of a requirements management initiative at Ericsson.Design/methodology/approachThe paper presents the initiative from three perspectives – the improvement initiative, the targeted software practices, and the environment.FindingsSPI initiatives easily get interrupted, are side‐tracked, and progress slowly due to changing environments. While most practitioners are painfully aware of this, the SPI literature has so far only touched on the issue. Agility principles would have helped Ericsson respond more effectively to events that impacted the initiative. Development of agile SPI practices requires coordination and alignment with other initiatives to develop agile software organizations.Originality/valueSPI has been adopted by many organizations to help them to deliver quality software. However, its success is a matter of debate and this paper deals with the issues involved.