Abstract

Software development organizations that rely on Capability Maturity Model Integration (CMMI) to assess and improve their processes have realized that agile approaches can provide improvements as well. CMMI and agile methods can work well together and exploit synergies that have the potential to improve dramatically business performance. The major question is: How to realize the integration of these two seemingly different approaches? In an earlier work, we have conducted a field study within six companies. These companies worked with agile methods for years and the Egyptian Software Engineering Competence Center (SECC), which is the regional CMMI appraisal center, assessed them. This study was mainly conducted to enhance the empirical understanding in this research field. Additionally, it showed that companies usually don’t use agile in a good way that helps in covering the CMMI specific practices. In this paper, we present a new approach for mapping between CMMI and Scrum method. This mapping has been analyzed, enhanced, and then applied to the same companies. Putting in considerations that other previous efforts have worked in the same context but for an older version of CMMI, our research is using the latest CMMI version, which is 1.3. The research shows that our mapping approach has resulted in 37% satisfaction and achieved 17% partial satisfaction for CMMI specific practices. This resembles 19.4% enhancement in the satisfaction, and 6.2% improvement in the partial satisfaction against the previous related research effort that was already not targeting the latest CMMI version.

Highlights

  • Quality management systems (QMS) like ISO 19011, Capability Maturity Model Integration (CMMI) or SPICE, have been a quite popular in the software industry since many years ago

  • It should be noted that the mapping between the specific practices of the CMMI process areas and Scrum practices according to Marcal et al considers the staged representation of CMMI-DEV version 1.2, but our work considers the CMMI-DEV version 1.3 which is the latest version till

  • In our previous research work [7], it was shown that working with agile could cover a portion of the CMMI specific practices with applying some non-scrum practices

Read more

Summary

INTRODUCTION

Quality management systems (QMS) like ISO 19011, CMMI or SPICE, have been a quite popular in the software industry since many years ago. The previously mentioned research showed that Scrum practices (as one of the Agile methods) with non-scrum improvements could satisfy the CMMI process areas’ specific practices. This means that an organization that uses Scrum without any www.ijacsa.thesai.org (IJACSA) International Journal of Advanced Computer Science and Applications, Vol 7, No 2, 2016 further improvements would not be able to achieve capability level 2 on Project Planning (PP), Project Management and Control (PMC), Requirements Management (REQM), Risk Management (RSKM), and Integrated Projected Management (IPM). This paper shows how the scrum practices and assets could cover the Project-Management category’s process areas of CMMI 1.3 with the use of normal scrum practices and assets without any extra enhancements.

Project Management Category of CMMI
Related Work
Research Questions
Defining Problem Solving Approach
STUDY ACTIVITIES
RESULTS
Future Work
CONCLUSION
Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call