Product Focused Software Process Improvement through Integrated Framework of Agile and CMMI: A Case in Small Settings

Full Text (PDF, 545KB), PP.55-67

Views: 0 Downloads: 0

Author(s)

Tatek Engdashet Kabitimer 1,* Dida Midekso 2 Ricardo J. Machado 3

1. IT Doctoral Program, Addis Ababa University, Addis Ababa, Ethiopia

2. Department of Computer Science, Addis Ababa University, Addis Ababa, Ethiopia

3. Department of Information Systems, University of Minho, Guimarães, Portugal

* Corresponding author.

DOI: https://doi.org/10.5815/ijitcs.2018.05.06

Received: 11 Apr. 2017 / Revised: 10 Nov. 2017 / Accepted: 19 Mar. 2018 / Published: 8 May 2018

Index Terms

Integrated framework of agile and CMMI, institutionalization, agile development, product-focused software process improvement

Abstract

Software process improvement (SPI) is an important requirement in a software company. The search for better approach brought different kinds of models with multiple sets of principles for SPI to be founded. The framework is proposed to mainly address an alternative way of achieving a better process capability. The approach focuses on the implementation of SPI which can seamlessly align with the organization nature, day to day business activities, and financial capability. The paper provides the detailed implementation guideline and application of the framework through case study results.

The case study is performed in a software development unit placed under academic institution. The unit is founded specifically for application development for internal and external customers. The case study is designed to be implemented in two software development projects in the development unit. From the ongoing case study, the results from the first project which is completed in six iterations are presented in this paper. Considering SPI implementation, the development team followed the framework and associated procedures throughout the development process. The results obtained in terms of aligning SPI to the daily development task and CMMI KPAs capability improvement achieved showed promising results.

Cite This Paper

Tatek Engdashet Kabitimer, Dida Midekso, Ricardo J. Machado, "Product Focused Software Process Improvement through Integrated Framework of Agile and CMMI: A Case in Small Settings", International Journal of Information Technology and Computer Science(IJITCS), Vol.10, No.5, pp.55-67, 2018. DOI:10.5815/ijitcs.2018.05.06

Reference

[1]Pino, Francisco J., Félix Garcia, and Mario Piattini. "Key processes to start software process improvement in small companies." Proceedings of the 2009 ACM symposium on Applied Computing. ACM, 2009 

[2]von Wangenheim, Christiane Gresse, Timo Varkoi, and Clênio F. Salviano. "Standard based software process assessments in small companies. “Software Process: Improvement and Practice 11.3 (2006): 329-335.

[3]Salviano, Clenio F., et al. "A method framework for engineering process capability models." 16th European Systems and Software Process Improvement and Innovation, Alcala, Spain (2009): 6-25.

[4]Pino, Francisco J., Félix García, and Mario Piattini. "Software process improvement in small and medium software enterprises: a systematic review." Software Quality Journal 16.2 (2008): 237-261.

[5]Dyba, Tore. "An empirical investigation of the key factors for success in software process improvement." IEEE Transactions on Software Engineering31.5 (2005): 410-424.

[6]Niazi, Mahmood, David Wilson, and Didar Zowghi. "Critical success factors for software process improvement implementation: an empirical study. “Software Process: Improvement and Practice 11.2 (2006): 193-211.

[7]von Wangenheim, Christiane Gresse, et al. "Systematic literature review of software process capability/maturity models." International Conference on Software Process Improvement and Capability Determination Spice. 2010. 

[8]von Wangenheim, Christiane Gresse, et al. "Creating software process capability/maturity models." IEEE software 27.4 (2010): 92-94.

[9]Baddoo, Nathan, and Tracy Hall. "Demotivators for software process improvement: An analysis of practitioners' views." Quality control and applied statistics 49.3 (2004): 341-342.

[10]Staples, Mark, et al. "An exploratory study of why organizations do not adopt CMMI." Journal of systems and software 80.6 (2007): 883-895.

[11]Wong, Bernard, and Sazzad Hasan. "Software Process Improvement in Bangladesh." Software Engineering Research and Practice. 2006.

[12]Babar, Muhammad Ali, and Mahmood Niazi. "Implementing software process improvement initiatives: an analysis of Vietnamese practitioners' views."2008 IEEE International Conference on Global Software Engineering. IEEE, 2008.

[13]S. Tessler and A. Barr, “Software R & D Strategies of Developing Countries,” pp. 1-17, 1996.

[14]Santos, Gleison, et al. "Implementing software process improvement initiatives in small and mediumsize enterprises in Brazil." Quality of Information and Communications Technology, 2007. QUATIC 2007. 6th International Conference on the. IEEE, 2007.

[15]Patel, Chetankumar, and Muthu Ramachandran. "Agile maturity model (AMM): A Software Process Improvement framework for agile software development practices." International Journal of Software Engineering, IJSE2.1 (2009): 3-28.

[16]Jakobsen, Carsten Ruseng, and Kent Aaron Johnson. "Mature Agile with a Twist of CMMI." Agile, 2008. AGILE'08. Conference. IEEE, 2008.

[17]Russwurm, W.: Hidden Treasure: The Implementation of CMMI Practices by Agile Methods. Procedures of the SEPG Conference (2010)

[18]Baker, Steven W. "Formalizing agility: an agile organization's journey toward CMMI accreditation." Agile Development Conference (ADC'05). IEEE, 2005.

[19]Marçal, Ana Sofia C., et al. "Blending Scrum practices and CMMI project management process areas." Innovations in Systems and Software Engineering 4.1 (2008): 17-29.

[20]M. Pikkarainen and A. Mäntyniemi, “An Approach for Using CMMI in Agile Software Development Assessments : Experiences from Three Case Studies,” in SPICE, 2006, no. May.

[21]Lukasiewicz, Katarzyna, and J. Miler. "Improving agility and discipline of software development with the Scrum and CMMI." IET software 6.5 (2012): 416-422.

[22]Anderson, David J. "Stretching Agile to fit CMMI level 3." Microsoft Corporation (2005).

[23]B. I. Benbasat, “The Case Research Strategy in Studies of Information Systems Case Research : Definition,” MIS Quarterly, vol. 11, no. 3, pp. 369-386, 1987. 

[24]Fritzsche, Martin, and Patrick Keil. "Agile methods and CMMI: compatibility or conflict?." e-Informatica Software Engineering Journal 1.1 (2007).

[25]T. Kähkönen and P. Abrahamsson, “Achieving CMMI Level 2 with Enhanced Extreme,” in PROFES, 2004, no, pp. 378-392.

[26]T. Engdashet, R. J. Machado, and D. Midekso, “Integrated Framework of Agile and CMMI : An Alternative Path towards Product Focused SPI for Small Companies,” Lecture Notes in Software Engineering, vol. 4, no. 1, pp. 1-6, 2016.

[27]Chrissis, Mary Beth, Mike Konrad, and Sandra Shrum. CMMI for development: guidelines for process integration and product improvement. Pearson Education, 2011.

[28]Tolbert, Pamela S., and Lynne G. Zucker. "The institutionalization of institutional theory." Studying Organization. Theory & Method. London, Thousand Oaks, New Delhi (1999): 169-184.

[29]Wiseman, E. R. I. C. A. "The institutionalization of organizational learning: A neoinstitutional perspective." Proceedings of OLKC (2007).

[30]Salo, Outi. "Improving software process in agile software development projects: results from two XP case studies." Euromicro Conference, 2004. Proceedings. 30th. IEEE, 2004.

[31]R. K. Yin, Case study research Design and Methods, 3rd ed. Delhi India: SAGE Publications, 2003.

[32]Per Runeson and Martin Höst, “Guidelines for conducting and reporting case study research in software engineering,” Empirical Software Engineering, vol. 14, no. 2, pp. 131-164, 2008.

[33]P. Runeson, M. H. St, A. Rainer, and B. R. Regnell, Case Study Research in Software Engineering: Guidelines and Examples. United States of America: John Wiley & Sons, Inc, 2012.

[34]Runeson, Per, and Martin Höst. "Guidelines for conducting and reporting case study research in software engineering." Empirical software engineering14.2 (2009): 131-164.

[35]Khan, M. Y. A., & Sayed, M. A. (2017). A Simple Software Engineering Environment for Coming Decades. International Journal of Education and Management Engineering (IJEME). 7(1) PP.46-53, 2017

[36]Ashraf, S., & Aftab, S. (2017). IScrum: An Improved Scrum Process Model. International Journal of Modern Education and Computer Science, 9(8), PP16-24. 2017