Abstract
Productive firms try to deliver high-quality products to be globally competitive. Therefore, software development firms need to adhere to a set of best practices that improve their processes. Capability maturity model integration (CMMI) comprehensively assesses the maturity of a firm's processes. Representing a major departure from the traditional method of running quality management in software development firms, the adoption of CMMI has major ramifications and long-lasting effects on a company’s quality procedures. Unfortunately, the literature lacks information as to how firms should implement CMMI. Our research involved conducting an exploratory study examining the major factors that influenced CMMI adoption for Jordanian software development firms. Quality managers from eighteen software development organizations took an open-ended survey. The results show that the main factors in CMMI implementation in Jordanian software development firms were issues of its being too costly, having no time, dealing with market scope, and lack of top management support. Conclusions are also presented.
Highlights
As software continues to intertwine with all aspects of our lives, we must pay more attention to the quality of software in both academia and industry
These results show that our respondents considered the following to be key factors in their decision-making process: being too costly, having no time, unclear market scope, and lacking top management support
SF2 highlighted the importance of cost saying, “Every penny a company plans to spend is usually studied for its return on investment (ROI)
Summary
As software continues to intertwine with all aspects of our lives, we must pay more attention to the quality of software in both academia and industry. The first is to assess the quality of the software after producing it by measuring non-functional requirements such as usability, reliability, and ease of learning. These describe the properties of software as a whole. The second way is to assess the quality of software by determining whether the steps of the process used to produce the software are correct. The search for ways to improve software quality has continued for many years, and software organizations have realized that one of their fundamental problems is the inability to effectively manage software processes (Butler, 1995; Pitterman, 2000; Yamamura, 1999). SPI is a long-standing approach to help organizations develop higher quality software more efficiently (Staples et al, 2007)
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
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
