Structural Analisys of CMMI with the Software Development Process, Project Portfolio Management and PMBOK
Abstract
Abstract. CMMI is one of the most used models in the software industry to certify the quality of its processes and products, reduces or eliminates rework, increases product and process reuse, reduces costs due to multiple evaluations and process improvement programs. On the other hand, companies that develop software apply traditional models or agile models, which manage the software development process. They also apply development standards such as ISO/IEC 12207 as well as project portfolio management standards and project management standards. The purpose of this paper is to relate the traditional and agile software development processes, project portfolio management and PMBOK with the CMMI standard. The results of this work allow us to determine the aspects that are missing from these standards and the best practices to reach a high level of CMMI maturity. It is concluded that for a company it is important to apply both agile processes and traditional processes, as well as all the standards that contribute improving the management of its projects. None of these practices and norms are opposed to the CMMI process areas, but rather are complemented to achieve a high level of quality in the final product and in achieving the objectives of the company.
References
[1] The Standish Group: Chaos Manifiesto 2013, http://www.versionone.com/assets/ img/files/CHAOSManifesto2013.pdf, (2013).
[2] ITIL, COBIT, CMMI, PMBOK: Como integrar y adoptar los estándares para un buen Gobierno de TI, http://helkyncoello.wordpress.com/2008/12/08/itil-cobit-cmmipmbok-como-integrar-y-adoptar-los-estandares-para-un-buen-gobierno-de-ti/.
[3] CMMI Institute: CMMI Institute - the home of Capability Maturity Model Integration, http://cmmiinstitute.com/.
[4] AESOFT: aesoft - Estudio de Mercado Sector Software y Hardware 2011, http://aesoft.com.ec/www/index.php/118-slideshow/154-http-www-slidesharenet-aesoft-ot-20489 microsoftfolleto.
[5] SEI: CMMI for SCAMPI SM Class A Appraisal Results 2012Mid-Year Update. Carnegie Mellon, USA (2012).
[6] Baker, S.W.: Formalizing agility, part 2: How an agile organization embraced the CMMI. In: Agile Conference, 2006. p. 8–pp. IEEE (2006).
[7] ISO: ISO/IEC 12207:2008, https://www.iso.org/obp/ui/#iso:std:iso-iec:12207:ed2:v1:en.
[8] José Sánchez del Rio: Qué es CMMI y para qué sirve -, http://www.cantabriatic.com/que-es-cmmi-y-para-que-sirve/, (2014).
[9] SEI: CMMI ® for Development, Version 1.3. Software Engineering Process Management Program (2010).
[10] Larrondo Petrie, M., Hugo, V., García, M., Giraldo, G.: Modelo de Registro y Acreditación de Instituciones de Educación Superior basado en el Modelo CMMI. In: San Cristóbal, Venezuela June 2-5, 2009 7 th Latin American and Caribbean Conference for Engineering and Technology WE1- 1 Seventh LACCEI Latin American and Caribbean Conferen ce for Engineering and Technology (LACCEI’2009) “Energy and Technology for the Americas: Education, Innovation, Technology and Practice.” Venezuela (2009).
[11] Anderson, D.: Kanban. Blue Hole Press (2010).
[12] ISO/IEC 12207: ISO/IEC 12207:2008 - Systems and software engineering – Software life cycle processes, http://www.iso.org/iso/catalogue_detail?csnumber=43447.
[13] Agile Aliance: Agile Alliance?:: The Twelve Principles of Agile Software, http://www .agilealliance.org/the-alliance/the-agile-manifesto/the-twelve-principles-ofagile-software/.
[14] Letelier, P., Penadés, M.C.: Métodologías ágiles para el desarrollo de software: eXtreme Programming (XP), http://www.cyta.com.ar/ta0502/v5n2a1.htm.
[15] Minna Pikkarainen, X.W.: An investigation of agility issues in scrum teams using agility indicators.
[16] Esfahani, H.C., Cabot, J., Yu, E.: Adopting agile methods: Can goal-oriented social modeling help? In: 2010 Fourth International Conference on Research Challenges in Information Science (RCIS). pp. 223–234 (2010).
[17] Ambler, S.: Quality in an agile world. Softw. Qual. Prof. 7, 34 (2005).
[18] Santos, M. de A.: Agile Practices: An Assessment of Perception of Value of Professionals on the Quality Criteria in Performance of Projects. J. Softw. Eng. Appl. 04, 700–709 (2011).
[19] Rothman, J.: Manage Your Project Portfolio: Increase Your Capacity and Finish More Projects. Pragmatic Bookshelf, Raleigh, N.C. (2009).
[20] Sowden, R.: Portfolio, Programme and Project Management Maturity Model, (2008).
[21] Scott Ambler: Gestión Ágil del Portafolio de Proyectos. Cut. IT J. (2009).
[22] Baschab, J., Piot, J.: The Executive’s Guide to Information Technology. John Wiley & Sons Inc (2007).
[23] Aguilar Alonso, I., Carrillo Verdún, J., Tovar Caro, E.: Importancia de la Gestión del Proceso de la demanda de TI, (2008).
[24] Thomason, D.: Strategic, tactical, operational [demand management]. Manuf. Eng. 83, 34–37 (2004).
[25] Aguilar Alonso, I., Carrillo Verdún, J., Tovar Caro, E.: Description of the structure of the IT demand management process framework. Int. J. Inf. Manag. 37, 1461–1473 (2017).
[26] Project Management Institute: Estandares en la gestión de Portafolios del PMI y PMBOK. (2006).
[27] F. Ghasemzadeh, N.P. Archer: Project portfolio selection through decision support. Decis. Support Syst. 29, 73–88 (2000).
[28] Marcal, A.S.C., de Freitas, B.C.C., Furtado Soares, F.S., Belchior, A.D.: Mapping CMMI project management process areas to SCRUM practices. In: Software Engineering Workshop, 2007. SEW 2007. 31st IEEE. pp. 13–22. IEEE (2007).