An evaluation of the RAPID assessment-based process improvement method for small firms

[Abstract]: With increasing interest by the software development community in software process improvement (SPI), it is vital that SPI programs are evaluated and the reports of lessons learned disseminated. This paper presents an evaluation of a program in which low-rigour, one-day SPI assessments were offered at no cost to 22 small Australian software development firms. The assessment model was based on ISO/IEC 15504 (SPICE). About twelve months after the assessment, the firms were contacted to arrange a follow-up meeting to determine the extent to which they had implemented the recommendations from the assessment. Comparison of the process capability levels at the time of assessment and the follow-up meetings revealed that the process improvement program was effective in improving the process capability of many of these small software development firms. Analysis of the assessment and follow-up reports explored important issues relating to SPI: elapsed time from assessment to follow-up meeting, the need for mentoring, the readiness of firms for SPI, the role of the owner/manager, the advice provided by the assessors, and the need to record costs and benefits. Based on a meta-analysis of the program and its outcomes, advice and recommendations are provided to small firms and assessors. As well as providing validation of the assessment model and method, the outcomes from this research have the potential to better equip practitioners and consultants to undertake software process improvement, hence increasing the success of small software development firms in domestic and global markets

Assessment of factors affecting the software process improvement in small organizations

Software process improvement implies a set of complex and systematic activities of software engineering. It requires theory and models established in management, technical and social sciences. The improvement is based on the assumption that the organization if it owns mature and capable processes, would be able to deliver quality software on time and in line with predicted costs. The maturity models are initially aimed for implementation in enterprise software organizations, government organizations and within the military industry. Their complexity and the size make them difficult to use in small software organizations and companies. In such organizations the interest for use and the efforts to make an efficient and effective organization is always presented, though. In this paper, the basic and derived capability maturity models are described and cases from their implementation are analyzed, along with assessment of results of such projects in business practices. The problem of the software process improvement in small organizations is described, extracting the risks and recommendations for its enhancement. These recommendations are provided in order to set up a foundation for implementation of these models in a specific managerial and organizational environment characterized by small organizations

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

Outsource the software process improvement consulting service: An alternative solution for small-settings

The focus of this paper is to outline the main structure of an alternative solution to implement a Software Process Improvement program in Small-Settings using the outsourcing infrastructure. This solution takes the advantages of the traditional outsourcing models and applies its structure to propose an alternative solution to make available a Software Process Improvement program for Small-Settings. With this outsourcing solution it is possible share the resources between several Small-Settings

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

A Process Asset Library to support Software Process Improvement in Small Settings

A main factor to the success of any organization process improvement effort is the Process Asset Library implementation that provides a central database accessible by anyone at the organization. This repository includes any process support materials to help process deployment. Those materials are composed of organization's standard software process, software process related documentation, descriptions of the software life cycles, guidelines, examples, templates, and any artefacts that the organization considers useful to help the process improvement. This paper describe the structure and contents of the Web-based Process Asset Library for Small businesses and small groups within large organizations. This library is structured using CMMI as reference model in order to implement those Process Areas described by this model

Expected requirements in support tool for software process improvement in SMEs

Nowadays being competitive is an important challenge for software development organizations. In order to achieve this, since last years, software process improvement has been an obvious and logical way. Unfortunately, even when many organizations are motivated to implement software process initiatives, not all know how best to do so, especially in Small and Medium Enterprises (SMEs) where due to its especial features, they have to be carefully in how to manage its resources to assure their market survival, Besides, even wen there has been developed models which pretend to help SMEs in the implementation of software process improvements, one of the main barrier that stopping SME's to implement software process improvements are the lack of knowledge and support of software process improvement. This paper presents and analysis of software process improvement at SMEs focusing on identifying on the once hand, SMEs features and success factors in the implementation of SPI initiatives. On the other hand, the expected requirements in a software tool focus on providing support for SMEs in the implementation of SPI initiatives

Structured software development with the IPIDDDT method - A lean method for small agile organizations

A software development process is a predetermined sequence of steps to create a piece of software. A software development process is used, so that an implementing organization could gain significant benefits. The benefits for software development companies, that can be attributed to software process improvement efforts, are improved predictability in the development effort and improved quality software products. The implementation, maintenance, and management of a software process as well as the software process improvement efforts are expensive. Especially the implementation phase is expensive with a best case scenario of a slow return on investment. Software processes are rare in very small software development companies because of the cost of implementation and an improbable return on investment. This study presents a new method to enable benefits that are usually related to software process improvement to small companies with a low cost. The study presents reasons for the development of the method, a description of the method, and an implementation process for the method, as well as a theoretical case study of a method implementation. The study's focus is on describing the method. The theoretical use case is used to illustrate the theory of the method and the implementation process of the method. The study ends with a few conclusions on the method and on the method's implementation process. The main conclusion is that the method requires further study as well as implementation experiments to asses the value of the method.Siirretty Doriast

Knowledge management in software process improvement: A case study of very small entities

This chapter discusses knowledge management (KM) aspects of how software process and software process improvement (SPI) is practiced within very small entities (VSEs) in the context of Irish software development industry. In particular, this study is concerned with the process of software development knowledge management in supporting the SPI. In order to understand the support process, the authors of this chapter have studied how KM processes are practiced within VSEs which includes communica- tion, learning, sharing, and documentation process. This study also focuses in detail on the issues of the knowledge atrophy problem in VSEs. The findings explain how KM has been practiced and influenced the software development process and process improvement in VSEs. This result indicates that KM processes in VSEs are being undertaken in a very informal manner and also in indirect way. This is due to a small team size, autonomous working and macro-management style and caused VSEs to be more informal in their KM processes specifically and SPI generally. In addition, the results have indicated that the informal environment and culture helped VSEs to easily create and share knowledge between staff members and also assisted VSEs to mitigate the knowledge atrophy problem in their organization