Introduction to the team software process
Introduction to the team software process
CMMI(R): Guidelines for Process Integration and Product Improvement (2nd Edition) (The SEI Series in Software Engineering)
An exploratory study of why organizations do not adopt CMMI
Journal of Systems and Software
Investigating software process in practice: A grounded theory perspective
Journal of Systems and Software
Systematic review: Systematic review of organizational motivations for adopting CMM-based SPI
Information and Software Technology
CMMI-ACQ: A Formal Implementation Sequences of the Processes Areas at Maturity Level 2
CERMA '08 Proceedings of the 2008 Electronics, Robotics and Automotive Mechanics Conference
Process improvement for small firms: An evaluation of the RAPID assessment-based method
Information and Software Technology
Perceived causes of software project failures - An analysis of their relationships
Information and Software Technology
| Hi-index | 0.00 |
SPI and in particular CMMI is being widely use by several organizations to improve their product quality. However, the SMEs are reluctant in adopting it and in particular maturity level 2 of CMMI, because they think that achieving this level is too expensive and do not see a clear benefit on it. Our solution to captivate the interest of SMEs in CMMI is the anticipation of some process areas of maturity level 3 considered as a benefit by the organization and implement those process areas at the same time of maturity level 2 of CMMI. In this paper, we identify the dependencies among all the process areas of CMMI and between all the process areas of each maturity level. Our study was conducted to identify the impact on the dependencies of maturity level 2 when we introduce some process areas of maturity level 3 in the implementation effort.