Organizational Change Perspectives on Software Process Improvement

Many software organizations have engaged in Software Process Improvement (SPI) and experienced the challenges related to managing such complex organizational change efforts. As a result, there is an increasing body of research investigating change management in SPI. To provide an overview of what we know and don’t know about SPI as organizational change, this paper addresses the following question: What are the dominant perspectives on SPI as organizational change in the literature and how is this knowledge presented and published? All journals on the AIS ranking list were screened to identify relevant articles and Gareth Morgan’s organizational metaphors (1996) were used to analyze this literature considering the following dimensions of each article: organizational perspective (metaphor), knowledge orientation (normative versus descriptive), theoretical emphasis (high versus low), main audience (practitioner versus academic), geographical origin (Scandinavia, the Americas, Europe, or the Asia-Pacific), and publication level (high versus low ranked journal). The review demonstrates that the literature on SPI as organizational change is firmly grounded in both theory and practice, and Scandinavia and the Americas are the main contributors to this research. The distribution of articles across Morgan’s metaphors is uneven and reveals knowledge gaps that present new avenues for research. The current literature offers important insights into organizational change in SPI from machine, organism, and brain perspectives. Practitioners may use these articles as a guide to SPI insights relevant to their improvement initiatives. In contrast, the impact of culture, dominance, psychic prison, flux and transformation, and politics in SPI have only received scant attention. We argue that these perspectives offer important insights into the challenges involved in managing change in SPI. Researchers are therefore advised to engage in new SPI research based on one or more of these perspectives. Overall, the paper provides a roadmap to help identify insights and specific articles related to SPI as organizational change.Software Process Improvement; Organizational Change; Organizational Metaphors; Images of Organization; Literature Review

Software Engineering Knowledge Areas in Startup Companies: A Mapping Study

Background - Startup companies are becoming important suppliers of innovative and software intensive products. The failure rate among startups is high due to lack of resources, immaturity, multiple influences and dynamic technologies. However, software product engineering is the core activity in startups, therefore inadequacies in applied engineering practices might be a significant contributing factor for high failure rates. Aim - This study identifies and categorizes software engineering knowledge areas utilized in startups to map out the state-of-art, identifying gaps for further research. Method - We perform a systematic literature mapping study, applying snowball sampling to identify relevant primary studies. Results - We have identified 54 practices from 14 studies. Although 11 of 15 main knowledge areas from SWEBOK are covered, a large part of categories is not. Conclusions - Existing research does not provide reliable support for software engineering in any phase of a startup life cycle. Transfer of results to other startups is difficult due to low rigor in current studies.Comment: Proceedings 6th International Conference on Software Business (ICSOB 2015), Braga, Portugal, 245-25

Organisational Size Metrics in IS Research: A Critical Survey of the Literature 1989 - 2000

A number of disciplines pursue research into organisations. This organisational research serves to improve knowledge regarding the interaction, behaviour and direction of humans and groups. Many of these disciplines use proprietary methods for and approaches to such research. Because Information Systems (IS) has drawn on several of these disciplines for foundation, a number of research approaches exist for examining organisations within the IS domain. Organisational size measurement, as one research approach in the IS literature, has received considerable application but little critical examination. This study examines six leading IS journals over an eleven year period in order to document and classify the metrics used for organisational size measurement in the IS research literature. The results show a large number of metrics in scholarly use, with studies offering little supportive discussion regarding the application of these metrics. The findings raise a number of issues that are out of the scope of this study: these issues merit further research

AHAA- Agile, Hybrid Assessment Method for Automotive, Safety Critical SMEs

The need for software is increasingly growing in the automotive industry. Software development projects are, however, often troubled by time and budget overruns, resulting in systems that do not fulfill customer requirements. Both research and industry lack strategies to combine reducing the long software development lifecycles (as required by time-to-market demands) with increasing the quality of the software developed. Software process improvement (SPI) provides the first step in the move towards software quality, and assessments are a vital part of this process. Unfortunately, software process assessments are often expensive and time consuming. Additionally, they often provide companies with a long list of issues without providing realistic suggestions. The goal of this paper is to describe a new low-overhead assessment method that has been designed specifically for small-to-medium-sized (SMEs) organisations wishing to be automotive software suppliers. This assessment method integrates the structured-ness of the plan-driven SPI models of Capability Maturity Model Integration (CMMI) and Automotive SPICETM with the flexibleness of agile practices

Virtualising Process Assessments to Facilitate Continual Service Improvement in IT Service Management

The IT Service Management (ITSM) industry has defined processes as best practices in the widely-accepted IT Infrastructure Library (ITIL) framework. However, studies on the measurement of ITSM process improvement are scant. Our research addressed the dual problems of the lack of transparency and the need for efficiency in ITSM process assessment. Using the Design Science Research methodology, we developed a Software-mediated Process Assessment (SMPA) approach that enables assessment of ITSM processes. The SMPA approach includes process selection; an online survey to collect assessment data; measurement of process capability; and reporting of process improvement recommendations. We implemented a decision support system (DSS) to automate the SMPA approach and evaluated it at two IT service providers. The evaluations indicated that the SMPA approach supports decision-making on process improvements. The findings provided design knowledge of virtualisation in ITSM process assessment and how this may facilitate continual service improvement

A Personnel-Driven Mini Assessment Approach for Supporting Continuous System and Software Process Improvement

Assessments are fundamental to the process improvement program of any organization in the software industry. Assessments provide a view of the state, capability, and maturity of processes in an organization relative to a reference model. Formal assessments are the most recognized, and are comprehensive in nature. Although the depth of their evaluation often results in significant process improvement opportunities, formal assessments are too costly for frequent use by many organizations. The interim between assessments typically leaves these organizations without the currency of process state information necessary to effectively drive continuous process improvement. Mini-assessments have emerged as a solution. This paper presents a mini-assessment approach that offers a substantial cost reduction compared to formal assessments and satisfies the process state currency requirement. A specification of the approach is given, followed by discussions on the process improvement possible with its use, comparisons to other assessment methods, and an example implementation

Virtualising process assessments to facilitate continual service improvement in IT service management

The IT Service Management (ITSM) industry has defined processes as best practices in the widely accepted IT Infrastructure Library (ITIL) framework. However, studies on the measurement of ITSM process improvement are scant. Our research addressed the dual problems of the lack of transparency and the need for efficiency in ITSM process assessment. Using the Design Science Research methodology, we developed a Software-mediated Process Assessment (SMPA) approach that enables assessment of ITSM processes. The SMPA approach includes process selection; an online survey to collect assessment data; measurement of process capability; and reporting of process improvement recommendations. We implemented a decision support system (DSS) to automate the SMPA approach and evaluated it at two IT service providers. The evaluations indicated that the SMPA approach supports decision-making on process improvements. The findings provided design knowledge of virtualisation in ITSM process assessment and how this may facilitate continual service improvement

A Conceptual MAP of Software Process Improvement

Software organisations have for many years struggled to mature engineering practices using a variety of approaches. Over the last decade a new approach, known as software process improvement (SPI), has emerged and become widely used in the software industry. In this paper we position SPI in the landscape of initiatives that can be used in software organisations to mature their operations. A map is offered describing the characteristic features of SPI initiatives, the benefits and risks related to such initiatives, and the relations to complementary approaches to professionalise the industry. The map highlights management, approach, and perspective as three main concerns of SPI and lists three key ideas for each of these concerns. The map is based on an extensive survey of the SPI literature combined with experiences from SPI practice. Practitioners can use the map strategically to make decisions on whether to initiate SPI initiatives, to integrate SPI efforts with other improvement initiatives, and, more generally, to create and manage improvement programs based on SPI ideas. Researchers can use the map to identify key questions and areas of knowledge that can fruitfully inform SPI theory and practice

Software development in startup companies: A systematic mapping study

Context: Software startups are newly created companies with no operating history and fast in producing cutting-edge technologies. These companies develop software under highly uncertain conditions, tackling fast-growing markets under severe lack of resources. Therefore, software startups present an unique combination of characteristics which pose several challenges to software development activities. Objective: This study aims to structure and analyze the literature on software development in startup companies, determining thereby the potential for technology transfer and identifying software development work practices reported by practitioners and researchers. Method: We conducted a systematic mapping study, developing a classification schema, ranking the selected primary studies according their rigor and relevance, and analyzing reported software development work practices in startups. Results: A total of 43 primary studies were identified and mapped, synthesizing the available evidence on software development in startups. Only 16 studies are entirely dedicated to software development in startups, of which 10 result in a weak contribution (advice and implications (6); lesson learned (3); tool (1)). Nineteen studies focus on managerial and organizational factors. Moreover, only 9 studies exhibit high scientific rigor and relevance. From the reviewed primary studies, 213 software engineering work practices were extracted, categorized and analyzed. Conclusion: This mapping study provides the first systematic exploration of the state-of-art on software startup research. The existing body of knowledge is limited to a few high quality studies. Furthermore, the results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context