FLEX-RCA: a lean-based method for root cause analysis in software process improvement
- 258 Downloads
Software process improvement (SPI) is an instrument to increase the productivity of, and the quality of work, in software organizations. However, a majority of SPI frameworks are too extensive or provide guidance and potential improvement areas at a high level, indicating only the symptoms, not the causes. Motivated by the industrial need of two Swedish automotive companies to systematically uncover the underlying root causes of high-level improvement issues identified in an SPI project—assessing inter-departmental interactions in large-scale software systems development—this paper advances a root cause analysis (RCA) method building on Lean Six Sigma, called Flex-RCA. Flex-RCA is used to delve deeper into challenges identified to find root causes as a part of the evaluation and subsequent improvement activities. We also demonstrate and evaluate Flex-RCA’s industrial applicability in a case study. An overall conclusion is that the use of Flex-RCA was successful, showing that it had the desired effect of both producing a broad base of causes on a high level and, more importantly, enabling an exploration of the underlying root causes.
KeywordsOrganizational management and coordination Communication Software engineering Software-intensive systems Automotive industry Case study Lean product development Agile Process improvement
The authors would like to express their gratitude to all those somehow involved in this study and especially the participants at Volvo Cars and Volvo Trucks.
- ABG. (1994). V-model: development standard for IT-systems of the Federal Republic of Germany. Lifecycle Process Model,Google Scholar
- Abran, A., Moore, J. W., et al. (2004). Guide to the software engineering body of knowledge (SWEBOK®). IEEE Computer Society Guide.Google Scholar
- Andersen, B., & Fagerhaug, T. (2000). Roo1 cause analysis: simplified tools and techniques. Milwaukee: ASQ Quality Press.Google Scholar
- Automotive SIG. (2010). The SPICE User Group, Automotive SPICE Process Assessment Model v2.5 and Process Reference Model v4.5, Available on: http://www.automotivespice.com. Accessed on Dec 2017.
- Beck, K. (2004). Extreme programming explained: embrace change (2nd ed.). Addison-Wesley.Google Scholar
- Breyfogle, F. W. (1999). Implementing Six Sigma: smarter solutions using statistical methods. New York: Wiley.Google Scholar
- Charfi, F., Sellami, F. (2004). Overview on dependable embedded systems in modern automotive. In: Proc. of the 2004 I.E. Int. Conference on Industrial Technology.Google Scholar
- CMMI. (2010). Capability Maturity Model Integration version 1.3. Technical report CMU/SEI-2010-TR-033. Software Engineering Institute (SEI). Available on: http://www.sei.cmu.edu/cmmi/. Accessed on Dec 2017.
- Gorschek, T., & Wohlin, C. (2004). Packaging software process improvement issues—a method and a case study. Software: Practice & Experience, 34, 1311–1344.Google Scholar
- Gorschek, T., Wohlin, C. (2003). Identification of improvement issues using a lightweight triangulation approach. In: The European Software Process Improvement Conference. Graz. Austria.Google Scholar
- Grimm, K. (2003). Software technology in an automotive company—major challenges. In: Proc. of the 25th International Conference on Software Engineering, IEEE.Google Scholar
- Hoerl, R. W. (1998). Six Sigma and the future of the quality profession. Quality Progress, 31, 35–42.Google Scholar
- Humphrey, W. S. (1989). Managing the software process. Reading: Addison-Wesley.Google Scholar
- ISO/IEC Std. 15504 (1998–2005): Information technology-process assessment, part 1 to part 5, International Organization for Standardization.Google Scholar
- Jalote, P., & Agrawal, N. (2005). Using defect analysis feedback for improving quality and productivity in iterative software development. In: Proc. of the Information Science and Communications Technology (ICICT 2005) (pp. 701–714).Google Scholar
- Kotonya, G., & Sommerville, I. (1998). Requirements engineering: processes and techniques. New York: John Wiley.Google Scholar
- Leszak, M., Perry, D. E., & Stoll, D. (2000). A case study in root cause defect analysis. Proc. of the 2000 International Conference on Software Engineering, 428–437.Google Scholar
- Morgan, J., & Bering-Jones, M. (2009). Lean Six Sigma for dummies. Chichester: Wiley.Google Scholar
- Paulk, M. C., Curtis, B., Chrissis, M. B., & Weber, C. V. (1994). The capability maturity model: guidelines for improving the software process. Reading: Addison-Wesley.Google Scholar
- Pernstal, J., Magazinius, A., & Gorschek, T. (2012). A study investigating challenges in the interface between product development and manufacturing in the development of software intensive automotive systems. International Journal of Software Engineering and Knowledge Engineering, 22(7), 965–1004.CrossRefGoogle Scholar
- Pernstal, J., Gorschek, T., Florén, D., & Feldt, R. (2013a). Software process improvement in inter-departmental development of software-intensive automotive systems—a case study, Product-focused software process improvement/lecture notes in computer science (Vol. 7983, pp. 93–107). Springer.Google Scholar
- Petersen, K., Feldt, R., Mujtaba, S., & Mattsson, M. (2008). Systematic mapping studies in software engineering. In 12th International Conference on Evaluation and Assessment in Software Engineering (pp. 71–80).Google Scholar
- Poppendieck, M., & Poppendieck, T. (2003). Lean software development: an agile toolkit. Addison-Wesley.Google Scholar
- Robson, C. (2002). Real world research: a resource for social scientists and practitioners-researchers (2nd ed.). Blackwell.Google Scholar
- SCAMPI-ADT. (2001). Standard CMMI Appraisal Method for Process Improvement (SCAMPI) version 1.1 (CMU/SEI-2001-HB-001) (p. 245). Pittsburgh: Carnegie Mellon SEI.Google Scholar
- Schwaber, K., & Beedle, M. (2001). Agile software development with Scrum. Upper Saddle River: Prentice Hall.Google Scholar
- Sivie, J., Forrester, E. (2004). Enabling technology transition using Six Sigma. In Bergey, J et al., Results of SEI independent research and development projects and report on emerging technologies and technology trends, (chapter 5) (CMU/SEI-2004-TR-018). Software Engineering Institute, Carnegie Mellon University, Pittsburgh. Available on: http://www.sei.cmu.edu/library/abstracts/reports/04tr018.cfm. Accessed on Dec 2016.
- Vanden Heuvel, L. N., Lorenzo, D. K., Hanson, W. E., Jackson, L. O., Rooney, J. R., & Walker, D. A. (2008). Root cause analysis handbook—a guide to efficient and effective incident investigation (3rd edn.). ABS Consulting ed.). Houston: Rothstein Associates Inc..Google Scholar
- Venkatesh Prasad, K., Broy, M., Krueger, I. (2010). Scanning advances in aerospace & automobile software technology. Proc. of the IEEE 2010; 98, 510–514.Google Scholar
- Volvo Cars. (2016). Available on https://www.media.volvocars.com/global/enhanced/en-gb/Media/Preview.aspx?mediaid=41678. Accessed on Dec. 2017.
- Volvo Trucks. (2016). Available on: http://www.volvotrucks.com/trucks/global/en-gb/newsmedia/quick_facts_about_volvo_trucks/pages/quick_facts_about_volvo_trucks.aspx . Accessed on Dec. 2017.
- Wheelwright, S. C., & Clark, K. B. (1992). Revolutionizing product development-quantum leaps in speed, efficiency, and quality. New York: Free.Google Scholar
- Wilson, P. F., Dell, L. D., & Anderson, G. F. (1993). Root cause analysis—a tool for total quality management. Milwaukee: American Society for Quality.Google Scholar
- Yin, R. (2003). Case study research: design and methods (3rd ed.). Thousand Oaks: Sage Publications Inc..Google Scholar
- Zahran, S. (1998). Software process improvement: practical guidelines for business success. Reading: Addison-Wesley.Google Scholar