Software process improvement in graduate software engineering programs

At the École de technologie supérieure (ÉTS), software process improvement (SPI) is taught in lecture format and with a 10-week implementation project in an organization by teams of students of the graduate software engineering curriculum. The SPI course is taught using a ‘problem- goal-solution’ approach where students learn that any process improvement initiative must be based on issues preventing an organization in achieving its organizational goals whether the organization is a company or a not-for- profit organization. An important aspect of this course is the management of technological change where students learn and put in practice in their project the ‘soft’ issues which are part of most SPI organizational initiatives

Using SPI Manifesto to Recover from CRM Deployment Project Failures and to Proactively Eliminate Similar Failures in Future: An Action Research Study in a Russian organization

The deployment of software products such as Customer Relationship Management systems may seem straightforward when reading the success stories of software providers. Yet, deployment projects are risky and often fail. Ineffective deployment processes of software providers and systems integrators are a major cause of failures. SPI Manifesto is a recent attempt to help the providers improve their processes, so most failures in software development may be eliminated proactively. Yet, the effectiveness and validity of SPI Manifesto relative to deployment projects are unclear. This paper presents an action research study in a customer organization to assess the extent to which SPI Manifesto could be used to help the providers to recover from situations in which CRM deployment projects are about to fail and to eliminate similar problems proactively in future. Based on the assessment, this paper contributes to improving the generic CRM deployment project process and SPI Manifesto

Process capability assessments in small development firms

[Abstract}: Assessment-based Software Process Improvement (SPI) programs such as the Capability Maturity Model (CMM), Bootstrap, and SPICE (ISO/IEC 15504) are based on formal frameworks and promote the use of systematic processes and management practices for software development. These approaches identify best practices for the management of software development and when applied, enable organizations to understand, control and improve development processes. The purpose of a SPI assessment is to compare the current processes used in an organization with a list of recommended or ‘best’ practices. This research investigates the adoption of SPI initiatives by four small software development firms. These four firms participated in a process improvement program which was sponsored by Software Engineering Australia (SEA) (Queensland). The assessment method was based on SPICE (ISO/IEC 15504) and included an initial assessment, recommendations, and a follow-up meeting. For each firm, before and after snapshots are provided of the capability as assessed on eight processes. The discussion which follows summarizes the improvements realized and considers the critical success factors relating to SPI adoption for small firms

A hierarchy of SPI activities for software SMEs: results from ISO/IEC 12207-based SPI assessments

In an assessment of software process improvement (SPI) in 15 software small- and –medium-sized enterprises (software SMEs), we applied the broad spectrum of software specific and system context processes in ISO/IEC 12207 to the task of examining SPI in practice. Using the data collected in the study, we developed a four-tiered pyramidal hierarchy of SPI for software SMEs, with processes in the higher tiers undergoing SPI in more companies than processes on lower level tiers. The development of the hierarchy of SPI activities for software SMEs can facilitate future evolutions of process maturity reference frameworks, such as ISO/IEC 15504, in better supporting software development in software SMEs. Furthermore, the findings extend our body of knowledge concerning the practice of SPI in software SMEs, a large and vital sector of the software development community that has largely avoided the implementation of established process maturity and software quality management standards

Using grounded theory to understand software process improvement: A study of Irish software product companies

Software Process Improvement (SPI) aims to understand the software process as it is used within an organisation and thus drive the implementation of changes to that process to achieve specific goals such as increasing development speed, achieving higher product quality or reducing costs. Accordingly, SPI researchers must be equipped with the methodologies and tools to enable them to look within organisations and understand the state of practice with respect to software process and process improvement initiatives, in addition to investigating the relevant literature. Having examined a number of potentially suitable research methodologies, we have chosen Grounded Theory as a suitable approach to determine what was happening in actual practice in relation to software process and SPI, using the indigenous Irish software product industry as a test-bed. The outcome of this study is a theory, grounded in the field data, that explains when and why SPI is undertaken by the software industry. The objective of this paper is to describe both the selection and usage of grounded theory in this study and evaluate its effectiveness as a research methodology for software process researchers. Accordingly, this paper will focus on the selection and usage of grounded theory, rather than results of the SPI study itself

Managerial commitment towards SPI in small and very small enterprises

This paper compares and contrasts the results of two similar studies into the software process practices in Irish Small and Very Small Enterprises. The first study contains rich findings in relation to the role and influence of managerial experience and style, with particular respect to the company founder and software development managers in small to medium seized enterprises (SMEs), whilst the second study contains extensive findings in relation to people and management involvement / commitment and SPI goal planning in very small enterprises (VSEs). By combining these results of these two studies of Irish SMEs/VSEs we can develop a rich picture of managerial commitment towards SPI and in particular explore the similarities between Small and Very Small Enterprises

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