Prescription, description, reflection: The shape of the software process improvement field

International Journal of Information Management

Volumn 24, Issue 6, 2004, Pages 457-472

  Hansen, Bo ^a   Rose, Jeremy ^b   Tjørnehøj, Gitte ^b  

^a Department of International Economics and Management   (Denmark)

^b AALBORG UNIVERSITY   (Denmark)

Author keywords

Capability maturity model; Literature review; Software process improvement

Indexed keywords

INFORMATION ANALYSIS; MATHEMATICAL MODELS; QUALITY CONTROL; RESEARCH; SOFTWARE ENGINEERING;

CAPABILITY MATURITY MODEL; LITERATURE REVIEW; SOFTWARE PROCESS IMPROVEMENT (SPI);

COMPUTER SOFTWARE;

EID: 7744242486     PISSN: 02684012     EISSN: None     Source Type: Journal    
DOI: 10.1016/j.ijinfomgt.2004.08.007     Document Type: Conference Paper

References (85)

1. Aaen, I., Arendt, J., Mathiassen, L., & Ngwenyama, O., 2001. A conceptual MAP of software process improvement. Scandinavian Journal of Information Systems, 13.
2. Aaen, I., Bøttcher, P., & Mathiassen, L. (1998). The Software Factory: Contributions and Illusions. Sixth European Conference on Information Systems (ECIS). France: Aix en Provence.
3. Abrahamsson, P. (2001). Rethinking the concept of commitment in software process improvement. Scandinavian Journal of Information Systems, 13, 69-98.
4. Abrahamsson, P. (2002). Commitment nets in software process improvement. Annals of Software Engineering, 14(1-4), 407-438.
5. Abrahamsson, P., & Kautz, K. (2002a). Personal software process - classroom experiences from Finland Proceedings of the seventh European conference on software quality. Finland: Helsinki.
6. Abrahamsson, P., & Kautz, K. (2002b). The personal software process - experiences from Denmark. Proceedings of the 28th EUROMICRO 2002 conference. Germany: Dortmund.
7. Ahern, D. M., Clouse, A., & Turner, R. (2001). CMMI Distilled: An Introduction to Multi-discipline Process Improvement. Reading, MA: Addison-Wesley.
8. Arent, J. (2000). Normative software process improvement. Department of Computer Science, Aalborg University.
9. Arent, J., & Nørbjerg, J. (2000). Software process improvement as organisational knowledge creation - a multiple case analysis. Proceedings of the 33rd Hawaii international conference on system sciences. Hawaii: Wailea.
10. Bach, J. (1994). The immaturity of the CMM. American Programmer, 7(9), 13-18.
11. Bach, J. (1995). Enough about process: what we need are heroes. IEEE Software, 12(2), 96-98.
12. Basili, V., Caldiera, G. (1995). Technical Report: CS-TR-3483, UMIACS-TR-95-67, Univeristy of Maryland, College Park, MD 20742, USA.
13. Basili, V., Caldiera, G., & Rombach, H. D. (1994a). The experience factory. Encyclopedia of software engineering - 2 Volume Set. New York: Wiley.
14. Basili, V., Caldiera, G., & Rombach, H. D. (1994b). The goal question metric approach. Encyclopedia of software engineering - 2 volume set. New York: Wiley p. 528-532.
15. Bhandari, I., Halliday, M., Tarver, E., Brown, D., Chaar, J., & Chillarege, R. (1993). A case-study of software process improvement during development. IEEE Transactions on Software Engineering, 19(12), 1157-1170.
16. Bilotta, J. G., & McGrew, J. F. (1998). A Guttman scaling of CMM level 2 practices: investigating the implementation sequences underlying software engineering maturity. Empirical Software Engineering, (3), 159-177.
17. Bollinger, T. B., & McGowan, C. (1991). A critical look at software capability evaluations. IEEE Software, 8(4), 25-41.
18. Borjesson, A., & Mathiassen, L. (2003). Making SPI happen: the IDEAL distribution of effort. System Sciences. Proceedings of the 36th annual Hawaii international conference . (pp. 328-337).
19. Brodman, J. G., & Johnson, D. L. (1994). What small businesses and small organizations say about the CMM. Proceedings of the 16th international conference on software engineering, Sorrento, Italy.
20. Campbell, M. (1995). Tool support for software process improvement and capability determination: Changing the paradigm of assessment. Software process newsletter. Silver Spring, MD: IEEE Computer Society (No. 4) p. 12-15.
21. Conradi, R., & Dingsoyr, T. (2000). Software experience bases: a consolidated evaluation and status report. Product Focused Software Process Improvement, 1840, 391-406.
22. Curtis, B. (1994). A mature view of the CMM. American Programmer, 7(9), 19-27.
23. Cusumano, M. A. (1989). The software factory: a historical interpretation. IEEE Software.
24. Deck, M. (2001). Managing process diversity while improving your practices. IEEE Software, 18(3), 21-27.
25. Deming, W. E. (1982). Out of the crisis. Cambridge, MA: Productivity Press.
26. Diaz, M., & Sligo, J. (1997). How software process improvement helped Motorola. IEEE Software, 14(5), 75-81.
27. Dion, R. (1992). Elements of a process-improvement program. IEEE Software, 9(4), 83-85.
28. Dion, R. (1993). Process improvement and the corporate balance sheet. IEEE Software, 10(4), 28-35.
29. Edgar-Nevill, V. M. A. (1994). Evaluation of the SEI software capability model within an information systems context; in pursuit of software quality. In: Ross, M., Brebbia, C. A., Staples, G., Stapleton, J. (Eds.). Software quality management II. Managing quality systems (Vol. 1, pp. 263-278). Computer Mechanical Publications.
30. El-Emam, K., Goldenson, D., McCurley, J., & Herbsleb, J. (2001). Modelling the likelihood of software process improvement: an exploratory study. Empirical Software Engineering, 6(3), 207-229.
31. Fayad, M. E., & Laitinen, M. (1997). Process assessment considered wasteful. Communications of the ACM, 40(11), 125-128.
32. Fernström, C. (1991). The Eureka software factory, concepts and accomplishments. Third European software engineering conference. Berlin: Springer.
33. Frederiksen, H. D., & Mathiassen, L. (2002). Diagnosing metrics practice in a software organisation. In Hariridranath, G., Rosenberg, D., & Sillince, J. A. A., et al. (Eds.), New perspectives on information systems development, theory, methods and practice. New York: Kluwer Academic.
34. Frederiksen, H. D., & Rose, J. (2003). The social construction of the software operation: reinforcing effects in metrics programs. Scandinavian Journal of Information Systems, 15, 23-38.
35. Gasston, J., & Halloran, P. (1999). Continuous software process improvement requires organisational learning: an Australian case study. Software Quality Journal, 8(1), 37-51.
36. Goldenson, D., & Herbsleb, J. D. (1995). After the appraisal: a systematic survey of process improvement, its benefits, and factors that influence success. CMU/SEI-95-TR-009. Software Engineering Institute, Pittsburgh, PA.
37. Haley, T. J. (1996). Software process improvement at Raytheon. IEEE Software, 13(6), 33-41.
38. Herbsleb, J., Carleton, A., Rozum, J., Siegel, J., & Zubrow, D. (1994a). Benefits of CMM-based software process improvement: executive summary of initial results. SPECIAL REPORT CMU/SEI-94-SR-013, Carnegie Mellon University.
39. Herbsleb, J., Carleton, A., Rozum, J., Siegel, J., & Zubrow, D. (1994b). Benefits of CMM-based software process improvement: initial results. CMU/SEI-94-TR-13, Software Engineering Institute, Pittsburgh, PA
40. Herbsleb, J. D., & Goldenson, D. R. (1996). A systematic survey of CMM experience and results. ICSE-18, IEEE.
41. Herbsleb, J. D., & Grinter, R. E. (1998). Conceptual simplicity meets organisational complexity: Case-study of a corporate metrics program. Proceedings of the 1998 international conference on software engineering: forging new links. Silver Spring, MD: IEEE Computing Society.
42. Herbsleb, J., Zubrow, D., Siegel, J., Rozum, J., & Carleton, A. (1994). Software process improvement: state of the payoff. American Programmer, 7(9), 2-12.
43. Hollenbach, C., Young, R., Pflugrad, A., & Smith, D. (1997). Combining quality and software improvement. Association for computing machinery. Communications of the ACM, 40(6), 41.
44. Hossein, S., & Kalyani, C. (1999). Towards an evaluative framework for software process improvement models. The Journal of Systems and Software, 47(2,3), 139.
45. Humphrey, W. S. (1995). A discipline for software engineering. Reading, MA: Addison Wesley Publishing Company.
46. Humphrey, W. S. (1997). Managing technical people - innovation, teamwork, and the software process. Pittsburgh: Addison-Wesley.
47. Humphrey, W. S. (1988). Characterizing the software process. IEEE Software, 5(2), 73-79.
48. Humphrey, W. S. (1998). Three dimensions of process improvement. Part I: process maturity, pp. 1-7.
49. Humphrey, W. S. (2002). Three process perspectives: organisations, teams, and people. Annals of Software Engineering, 14(1-4), 39-72.
50. Humphrey, W. S., Snyder, T. R., & Willis, R. R. (1991). Software process improvement at Hughes aircraft. IEEE Software, 8(4), 11-23.
51. Iversen, J. (2000). Data-driven intervention in software process improvement. Department of Computer Science, Aalborg University.
52. Iversen, J., & Mathiassen, L. (2003). Cultivation and engineering of a software metrics program. Information Systems Journal, 13(1), 3-19.
53. Iversen, J., Nielsen, P. A., & Nørbjerg, J. (1999). Situated assessment of problems in software development. The DATABASE for advances in information systems, 30(2).
54. Johnson, D., & Brodman, J. (1996). Realities and rewards of software process improvements. IEEE Software, 13(6), 99-101.
55. Johnson, D. L., & Brodman, J. G. (1995). Return on investment (ROI) from software process improvement as measured by US industry. Software process - improvement and practice, 1(1), 35-47.
56. Juran, J. M., & Gryna, F. (1988). Juran's quality control handbook. New York: McGraw-Hill Book Company.
57. Kautz, K., & Thaysen, K. (2001). Knowledge, learning and IT support in a small software company. Journal of Knowledge Management, 5(4), 349-357.
58. Kautz, K. H., Hansen, H. W., & Thaysen, K. (2000). Applying and adjusting a software process improvement model in practice: the use of the IDEAL model in a small software enterprise. Limerick, Ireland: International Conference on Software Engineering.
59. Kautz, K. H., Thaysen, K., & Vendelø, M. T. (2002). Knowledge creation and IT systems in a small software firm. Journal of OR Insight.
60. Kelly, D. P., & Culleton, B. (1999). Process improvement for small organisations. Computer, 32(10), 41.
61. Kohutek, H. J. (1996). Reflections on the capability and maturity models of engineering processes. Quality and Reliability Engineering International, 12(3), 147-155.
62. Konrad, M., Chrissis, M. B., Ferguson, J., Garcia, S., Hefley, B., Kitson, D., & Paulk, M. (1996). Capability maturity modeling at the SEI. Software Process - Improvement and Practice, 2(1), 21-34.
63. Kuhn, T. (1962). The structure of scientific revolutions. Chicago: Chicago University Press.
64. Kuvaja, P. (1999). BOOTSTRAP 3.0 - A SPICE1 conformant software process assessment methodology. Software Quality Journal (8), 7-19.
65. Kuvaja, P., & Bicego, A. (1994). BOOTSTRAP - a European assessment methodology. Software Quality Journal, 3(3), 117-127.
66. Kuvaja, P., Palo, J., & Bicego, A. (1999). TAPISTRY - a software process improvement approach tailored for small enterprises. Software Quality Journal, 8(2), 149-156.
67. Kuvaja, P., Similä, J., Krzanik, L., Bicego, A., Saukkonen, S., & Koch, G. (1994). Software process assessment & improvement - the bootstrap approach. Oxford: Blackwell Publisher.
68. Laporte, C., & Papicco, N. (1998). Software and systems engineering process development and integration at Oerlikon aerospace. Software Process Newsletter, 11, 10-17.
69. Larsson, S., & Kolb, P. (2002). Software process improvement at ABB. Proceedings of the Institution of Civil Engineers-Civil Engineering, 150, 46-49.
70. Lyytinen, K., Mathiassen, L., & Ropponen, J. (1998). Attention shaping and software risk, a categorial analysis of four classical approaches. Information Systems Research, 9(3).
71. Mathiassen, L., Pries-Heje, J., & Ngwenyama, O. (Eds.) (2002). Improving software organisations: from principles to practice. Reading, MA: Addison-Wesley.
72. Matsumoto, Y. (1981). SWB System: A software factory. Amsterdam: North-Holland.
73. Matsumoto, Y. (1987). A software factory: an overall approach to software production. London: IEEE.
74. Mintzberg, H. (1990). Strategy formation: schools of thought. In Fredrickson, J. W. (Ed.), Perspectives on strategic management. New York: Harper Business.
75. Ngwenyama, O., & Nielsen, P. A. (2003). Competing values in software process improvement: an assumption analysis of CMM from an organisational culture perspective. IEEE Transactions on Engineering Management, 50(1), 100-112.
76. Paulk, M. C., Curtis, B., Chrissis, M. B., & Weber, C. (1993). Capability maturity model for software version. 1.1. Pittsburgh, PA: Software Engineering Institute.
77. Paulk, M. C., Weber, C., Curtis, B., & Chrissis, M. B. (1995). The capability maturity model: guidelines for improving the software process. Reading, MA: Addison Wesley.
78. Pulford, K., Kuntzmann-Combelles, A., Shirlaw, S., & Harutunian, K. (1992). A quantitative approach to software management: the AMI handbook. London: CSSE South Bank University.
79. Reifer, D. J. (Ed.). (2002). The CMMI: it's formidable [Guest editor's corner]. The Journal of Systems and Software, 50, 97-98.
80. Schein, E. (1973). Professional education. New York: McGraw-Hill.
81. Schon, D. (1983). The reflective practitioner: how professionals think in action. New York: Basic Books.
82. Weber, H. (1997). The software factory challenge. Amsterdam: IOS Press.
83. Webster, J., & Watson, R. T. (2002). Editorial: analyzing the past to prepare for the future: writing a literature review. MIS Quarterly, 26(2), xiii-xxiii.
84. Wiegers, K. (1999). Software process improvement in web time. IEEE Software, 16(4), 78-86.
85. Wohlwend, H., & Rosenbaum, S. (1994). Schlumberger's software improvement program. IEEE Transactions on Software Engineering, 20(11), 833-839.