Combining CMMI Specific Practices with Scrum Model to Address Shortcomings in Process Maturity

Abstract

Software process improvement (SPI) is the approach to understand the software development process lifecycle and implement necessary changes to achieve a high-quality, maintainable product. The software industry is comprised of small and medium-sized enterprises that adopt agile models as their preferred model of development. The Capability Maturity Model Integration (CMMI) model for software process improvement and quality is used to address aspects of software quality and maturity that Scrum was not initially designed to consider. CMMI is used for its reliable practices and consideration of many aspects of software development in process, project and product. After consideration of literature, three process areas are selected to address necessary elements in Scrum used by software developers in offshoring destinations. The practices are selected based on their practicality in small, agile settings and the ability to be incorporated into Scrum activities without disrupting the models sprint cycles. This opens the way for smaller enterprises to create produce quality.