An Enhanced Action Research Approach for Managing Risks in Software Process Improvement

Full Text (PDF, 224KB), PP.24-30

Views: 0 Downloads: 0


Faiza Ayub Syed 1,* Kokub Sultan 1 Engr Ali Javed 1

1. Department of Software Engineering, University of Engineering & Technology, Taxila, Pakistan

* Corresponding author.


Received: 10 Feb. 2013 / Revised: 11 Apr. 2013 / Accepted: 2 May 2013 / Published: 8 Jun. 2013

Index Terms

Software Process Improvement (SPI), Collaborative Practice Research (CPR), Enhanced Collaborative Practice Research (ECPR).


Managing risks in Software Process Improvement (SPI) is a key point of software success. A software risk is considered as an essential characteristic of software development process which if ignored will increase the chance of project failure. For this purpose different risk management approaches are developed. These approaches lead to the identification, assessment and control of risk occurrence in software projects. Collaborative Practice Research (CPR) is one of the action research approaches for managing risk in SPI. In this approach the focus is on gathering information regarding SPI and acknowledging risk management in process development by developing risk assessment strategies and models. The main challenge of this action research approach is to validate the developed risk approach. This paper has a critical review on the existing research approach i.e. CPR. It also provides an enhanced form of CPR which modifies the current CPR approach by including a risk validation activity.

Cite This Paper

Faiza Ayub Syed, Kokub Sultan, Ali Javed, "An Enhanced Action Research Approach for Managing Risks in Software Process Improvement", International Journal of Modern Education and Computer Science (IJMECS), vol.5, no.6, pp. 24-30, 2013. DOI:10.5815/ijmecs.2013.06.04


[1]Bob McFeeley, “IDEALSM: A User’s Guide for Software Process Improvement”, February 1996.
[2]Rini van Solingen, “Measuring the ROI of Software Process Improvement”, IEEE, 2004. DOI:10.1109/MS.2004.1293070.
[3]Xu Ru-zhi, “Optimizing software process based on risk assessment and control”, IEEE, September 2005. DOI:10.1109/CIT.2005.151.
[4]John E. Ettlie, Jorg M. Elsenbach, “Modified Stage-Gate® Regimes in New Product Development”, Journal of Project Innovation Management, 2006. DOI:10.1111/j.1540-5885.2006.00230.x.
[5]Zhedan Pan, Hyuncheol Park, Jongmoon Baik, Hojin Choi, “A Six Sigma Framework for Software Process Improvements and its Implementation”, 14th Asia-Pacific Software Engineering Conference, IEEE, 2007. DOI:10.1109/ASPEC.2007.43.
[6]Yonghui CAO, Xin Xiang,"Software Process Improvement Framework Based on CMMI Continuous Model Using QFD" in proceedings of International Journal of Computer Science Issues, 2013.
[7]Ray C. Williams, "The CMMI RSKM Process Area as a Risk Management Standard" in proceedings of Sixteenth Annual International Symposium of the International Council On Systems Engineering, July 2006.
[8]Geir Sigurour Jonsson, "A Case Study into the Effects of Software Process Improvement on Product Quality", June 2004.
[9]Jakob H. Iversen, Lars Mathiassen, “Managing Risk in Software Process Improvement: An Action Research Approach”, September 2004.
[10]Mohd Hairul Nizam Md. Nasir, Rodina Ahmad, Noor Hafizah Hassan, “Resistance Factors in the Implementation of Software Process Improvement Project”, IEEE, ITSim 2008. DOI:10.1109/ITSIM.2008.4631933.
[11]Stefan Biffla, Christian Dengerb, Frank Elberzhagerb, Dietmar Winklera, “Quality Assurance Tradeoff Analysis Method (QATAM), An Empirical Quality Assurance Planning and Evaluation Framework”, 2008.
[12]Suphak Suwanya, Werasak Kurutach, “An Analysis of Software Process Improvement for Sustainable Development in Thailand”, IEEE, 2008. DOI:10.1109/CIT.2008.4594764.
[13]Dan Taylor, Gary McGraw, “Adopting a Software Security Improvement Program”, May/June 2005. DOI:10.1109/MSP.2005.60.
[14]Jakub Miler1, Janusz Gorski, “Risk-driven Software Process Improvement - a Case Study”, EuroSPI, 2004.
[15]Gary Stoneburner, Alice Goguen, Alexis Feringa, “Risk Management Guide for Information Technology Systems”, NIST Special Publication 800-30, July 2002.
[16]Dr. Robert Cooper, Dr. Scott Edgett, “Stage-Gate® - Your Roadmap for New Product Development”,, 1996-2013.