Investigating the role of CMMI with expanding company size for small‐ to medium‐sized enterprises

Abstract

In this article we show how the results from software process appraisals of ten small‐ to medium‐sized software development enterprises demonstrate that as companies become larger they naturally use an increasing number of practices within the Capability Maturity Model Integration (CMMI®). The companies involved in this study had no CMMI® experience prior to this work. We identify those practices that tend to be best followed by both small‐ and medium‐sized enterprises and those that tend to be introduced as the company size increases from small to medium. We conclude that the CMMI® appears to have an inherent roadmap for process improvement, buried within its explicit structure of capability levels that is driven by company expansion. The results of this study can be used by organisations to plan process improvement as they expand in size and staff complement. We further show how our results are consistent with the European Union's definition of a ‘Small’ and a ‘Medium’ sized enterprise. Copyright © 2009 John Wiley & Sons, Ltd.

XP in a Small Software Development Business: Adapting to Local Constraints

“…Like the small team within a larger company, small shops have little need for elaborate plans, change management procedures or document-based coordination and communication in general [14,15]. However, a small team working in a large company often has access to resources not found in the small company setting.…”

“…designed around frequent and incremental deliveries, and a workable channel for rapid customer feedback for revised requirements [3]. The family of agile software development methods, which research has shown to be suited to the small team environment, seems to fit these conditions of the small shop software shop [14,15].…”

“…The sum of the constraints faced by small software shops implies that the methods, tools, and techniques traditionally recommended in software engineering, which have been evolved over the long term in the context of the large team and/or large company, do not fit well with the small software company [3,14,15,16]. This does not imply, however, that a small software shop should not strive towards a systematic and professional software development process [6,14,15,16], but that methods and processes used must be adapted to the small-shop environment and constraints; i.e.…”

“…This does not imply, however, that a small software shop should not strive towards a systematic and professional software development process [6,14,15,16], but that methods and processes used must be adapted to the small-shop environment and constraints; i.e. designed around frequent and incremental deliveries, and a workable channel for rapid customer feedback for revised requirements [3].…”

A proposed model for reuse of software requirements in requirements catalog

“…According to Barry Boehm , there are three things that can improve project efficiency: work faster, work in smarter way or work less. Clearly, reuse is an optimal alternative for the last issue, although it may be the answer to all three.…”