Conceptualization and Measurement of the Capability Maturity Model (CMM): An Examination of Past Practices and Suggestions for Future Applications

The Capability Maturity Model (CMM) has obtained world-wide status as a premier process improvement framework. This influence has not gone unnoticed by the academic community who has utilized the CMM as a key construct representing a firm’s IT project management and development capabilities. However, an examination of the current state of research reveals no consensus on how to best operationalize CMM-based process capability; therefore, this study seeks to start a dialog in the academic community about how CMM-based process capability should be conceptualized and measured. While the results do suggest that CMM-based process capability is multidimensional, and that a process structure rather than a level structure may be the most appropriate; the main intent of this research is to call attention to the need for greater rigor in the measurement and conceptualization of CMM-based process capability in the academic literature. The hope is this research represents a first step in developing a fully refined and validated CMM-based process capability measure

Metrics and Models for Cost and Quality of Component-Based Software

Quality and risk concerns currently limit the application of commercial off-the-shelf (COTS) software components to non-critical applications. Software metrics can quantify factors contributing to the overall quality of a component-based system, and models for tradeoffs between cost and various aspects of quality can guide quality and risk management by identifying and eliminating sources of risk. This paper discusses metrics and models that can be used to alleviate quality concerns for COTS-based systems, enabling the use of COTS components in a broader range of applications

The effect of reusability on perceived competitive performance of Australian software firms

This study set out to investigate how software firms can manage their software development efforts in order to compete effectively. Based on previous studies, a research model was developed. Reusability was expected to positively influence process flexibility, process productivity and process predictability. In turn these software process performance dimensions were expected to influence perceived competitive performance, assessed in terms of market responsiveness and product cost efficiency. Three hundred and twenty organisations were surveyed. In the data reduction stage, the research model was revised and process efficiency, technoregulatory flexibility, process effectiveness and labour flexibility resulted as the new software process performance variables. The revised model was tested and findings indicate that there is a relationship between reusability and techno-regulatory flexibility and market responsiveness

Making SPI Happen: The Roads to Process Implementation

Software Process Improvement (SPI) has been widely adopted by software organizations to enhance their capability to effectively deliver quality software. The approach has several positive merits. But many initiatives fail because the software processes are never adopted in practice. This paper offers a comparative analysis of the implementation strategies and outcomes of 18 SPI initiatives within Ericsson. The analysis draws upon concepts from the diffusion of innovations literature and leads to four different process implementation strategies – High Way, Country Road, Crossroads, and Dead End Street. These roads to software process implementation target different levels of practice and they rely on different mixtures of process push and practice pull. Our research suggests that the High Way with its combination of strong push and strong pull is the most promising road to implementation success, whereas the other roads imply serious barriers to success

The adoption of software process improvement (SPI) program in the construction industry

Integrating the design process and automating the construction process are called for in the Industrialised Building System (IBS) Roadmap 2003-2010 and the Construction Industry Master Plan (CIMP) 2006-2015. Hence, the industry needs to improve the construction delivery process by having as many processes utilizing advanced IT/ICT technologies. With a goal of producing zero product failure and meeting the users’ requirement satisfaction, this is an initial study into automating the construction tasks by studying a systematic process management commonly used for software implementation. We present a feasibility study on the use of a Software Process Improvement (SPI) Program in an IT organization—assuming that the construction organization will become an implementer of computer-integrated procedures in the future. Based on a case study conducted at a local IT software company, it documents the implementation of a SPI program to improve the internal software process development. The study uses the Capability Maturity Model Integration (CMMI) from Software Engineering Institute as SPI framework and IDEAL model-SPI life cycle model for executing and managing SPI program. Results show that the SPI Program model is successful in terms of the IT organization increasing its work productivity, high end-user product satisfaction and reduction of software defects. The paper concludes with discussions on how we can bridge computer science approach into the construction industry, thereby contributing to the development of future theoretical and application methodologies towards applying IT/ICT initiatives in the local construction industry

Challenging Software Process Improvement by Design

Software process improvement (SPI) today is based mainly on a perception of software processes as artifacts and this perception has led SPI efforts to focus on perfecting such artifacts as a means to improve the practices of the people supposed to execute these software processes. Such SPI efforts thus tend to view the design of software processes as separate from their use. In this approach process designers are expected to provide process knowledge to software developers, and software developers are expected to provide experiences and problems to the process designers. This focus on software processes as artifacts implies an emphasis on formalization and externalization of process models possibly at the expense of the process knowledge in the heads of the process users. The paper point to problems related to separation and externalization from a theoretical standpoint and suggests an alternative to Improvement by Design: End-user SPI, where process users individually and collectively design their own software processes assisted by process experts

Impact of the Journey: IS Employee Attitudes and Perceptions as Organizations Climb the CMM Ladder

We surveyed 736 IS professionals in organizations at varying levels of the Capability Maturity Model (CMM) to investigate job attitudes and perceptions. Although anecdotal reports and the scant preliminary empirical studies to-date suggest job attitudes and perceptions improve for employees as organizations climb the CMM ladder, we found evidence of a more complex picture. IS workers reported significantly lower professional efficacy and affective commitment in organizations at CMM Level 3 than in organizations at Level 1, and reports of cynicism were higher in organizations at upper levels of the CMM

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

Spreadsheets and Sarbanes-Oxley: Regulations, Risks, and Control Frameworks

The Sarbanes-Oxley Act of 2002 (SOX) forced corporations to examine their spreadsheet use in financial reporting. Corporations do not like what they are seeing. Surveys conducted in response to SOX show that spreadsheets are used widely in corporate financial reporting. Spreadsheet error research, in turn, shows that nearly all large spreadsheets contain multiple errors and that errors of material size are quite common. The first round of Sarbanes-Oxley assessments confirmed concerns about spreadsheet accuracy. Another concern is spreadsheet fraud, which also exists in practice and is easy to perpetrate. Unfortunately, few organizations maintain effective controls to deal with either errors or fraud. This paper examines spreadsheet risks for Sarbanes-Oxley (and other regulations) and discusses how general and IT-specific control frameworks can be used to address the control risks created by spreadsheets