SPI agility: How to navigate improvement projects

Software Process Improvement and Practice

Volumn 12, Issue 3, 2007, Pages 267-281

  Aaen, Ivan ^a   Börjesson, Anna ^a   Mathiassen, Lars ^a  

^a AALBORG UNIVERSITY   (Denmark)

Author keywords

Agility; Governance mechanisms; Project tactics; Software process improvement

Indexed keywords

GOVERNANCE MECHANISMS; PROJECT TACTICS; SOFTWARE PROCESS IMPROVEMENT;

ADAPTIVE SYSTEMS; PROCESS ENGINEERING; PROJECT MANAGEMENT;

SOFTWARE ENGINEERING;

EID: 34250735046     PISSN: 10774866     EISSN: 10991670     Source Type: Journal    
DOI: 10.1002/spip.309     Document Type: Article

References (47)

1. Aaen I. 2002. Challenging software process improvement by design. Paper Presented at the Proceedings of Xth European Conference on Information Systems, Gdansk, Poland, June 6-8.
2. Aaen I. 2003. Software process improvement: blueprints versus recipes. IEEE Software 20(5): 86-93.
3. Abrahamsson P. 2001. Rethinking the concept of commitment in software process improvement. Scandinavian journal of Information Systems 13: 69-98.
4. Abrahamsson P, Salo O, Ronkainen J, Warsta J. 2002. Agile Software Development Methods - Review and Analysis (No. 51-38-6010-8). VTT Electronics: Oulu, Finland.
5. Baddoo N, Hall T. 2002. Practitioner roles in software process improvement: an analysis using Grid Technique. Software Process-Improvement and Practice 7(1): 17-31.
6. Bartunek JM, Louis MR. 1996. Insider/outsider Team Research. Sage Publications.
7. Baskerville R, Levine L, Pries-Heje J, Ramesh B, Slaughter S. 2001. How internet software companies negotiate quality. Computer 34(5): 51-57.
8. Beck K. 2000. Extreme Programming Explained: Embrace change. Addison-Wesley: Reading, MA.
9. Börjesson A, Mathiassen L. 2004a. Making SPI Happen: the road to process implementation. Paper presented at the European Conference on Information Systems (ECIS 2004): The European Information Systems Profession in the Global Networking Environment. Turku School of Economics and Business Administration: Finland, June 14-16.
10. Börjesson A, Mathiassen L. 2004b. Successful process implementation. IEEE Software 21(4): 36-44.
11. Börjesson A, Mathiassen L. 2005. Improving software organizations: agility challenges and implications. Information Technology & People 18(4): 359-382.
12. CMMI Product Team. 2002a. CMMI for software engineering, version 1.1, continuous representation (CMMI-SW, VI.1, Continuous). (Technical Report No. CMU/SEI-2002-TR-028), Software Engineering Institute: Pittsburgh, PA.
13. CMMI Product Team. 2002b. CMMI for software engineering, version 1.1, staged representation (CMMISW, VI.1, Staged). (Technical Report No. CMU/SEI-2002-TR-029), Software Engineering Institute: Pittsburgh, PA.
14. Creech B. 1994. The Five Pillars of TQM: How to Make Total Quality Management Work for You. Truman Talley Books/Dutton: New York.
15. Dove R. 2001. Response Ability-The Language, Structure, and Culture of the Agile Enterprise. Wiley: New York.
16. Fayad ME, Laitinen M. 1997. Thinking objectively -process assessment considered wasteful. Communications of the ACM 40(11): 125-128.
17. Feiler PH, Humphrey WS. 1991. Software Process Development and Enactment: Concepts and Definitions (No. CMU/SEI-92-TR-004). Software Engineering Institute: Pittsburgh, PA.
18. Fowler P, Rifkin S. 1990. Software Engineering Process Group Guide No. CMU/SEI-90-TR-24). Software Engineering Institute: Pittsburgh, PA.
19. Galbraith J. 1973. Designing Complex Organizations. Addison-Wesley: Reading, MA.
20. Grady RB. 1997. Successful Software Process Improvement. Prentice Hall: Upper Saddle River, NJ.
21. Gunneson AO. 1997. Transitioning to Agility - Creating The 21st Century Enterprise. Addison-Wesley: Reading, MA.
22. Haeckel SH. 1995. Adaptive enterprise design: the sense-and-respond model. Planning Review 23(3): 6-42.
23. Haeckel SH. 1999. Adaptive Enterprise: Creating and Leading Sense-and-respond Organizations. Harvard Business School Press: Boston, MA.
24. Holmberg L, Mathiassen L. 2001. Survival patterns in fast-moving software organizations. IEEE Software 18(6): 51-55.
25. Humphrey WS. 1989. Managing the Software Process, 1st edn. Addison-Wesley Publishing Company: Reading, MA.
26. Kautz K, Hansen H W, Thaysen K. 2001. Understanding and changing software organisations: an exploration of four perspectives on software process improvement. Scandinavian Journal of Information Systems 13:31-50.
27. Kondo Y. 2000. Innovation versus standardization. TQM Magazine 12(1): 6-10.
28. Mathiassen L. 2002. Collaborative practice research. Information Technology & People 15(4): 321-334.
29. Mathiassen L, Pries-Heje J, Ngwenyama O. 2002. Improving Software Organizations. Addison-Wesley: Boston, MA.
30. McFeeley B. 1996. IDEAL: A User's Guide for Software Process Improvement (Handbook No. CMU/SEI-96-HB-001). SEI: Pittsburgh, PA.
31. Middleton P. 1997. Managing software quality by standardization. Software Process-Improvement and Practice 3(4): 201-212.
32. Mingers J. 2001. Combining IS research methods: towards a pluralist methodology. Information Systems Research 12(3): 240-259.
33. Orlikowski WJ. 1996. Improvising organizational transformation over time: a situated change perspective. Information Systems Research 7(1): 63-92.
34. Osterweil LJ. 1987. Software processes are software too. Paper Presented at the Proceedings of the Ninth International Conference on Software Engineering, Monterey, CA, March.
35. Osterweil LJ. 1997. Software processes are software too, revisited. Paper Presented at the Proceedings of the 19th International Conference on Software Engineering, May 1997: Pittsburgh, PA.
36. Paulk MC, Curtis B, Chrissis MB, Weber CV. 1993a. Capability maturity model for software, version 1.1. Technical Report No. CMU/SEI-93-TR-24, Software Engineering Institute: Pittsburgh, PA.
37. Paulk MC, Weber CV, Garcia SM, Chrissis M, Bush M. 1993b. Key practices of the capability maturity model, version 1.1. Technical Report No. CMU/SEI-93-TR-25, Software Engineering Institute: Pittsburgh, PA.
38. Paulk MC, Weber CV, Curtis B, Chrissis MB. 1995. The Capability Maturity Model : Guidelines for Improving the Software Process. Addison-Wesley Pub. Co: Reading, MA.
39. Pries-Heje J, Tryde S. 2001. Diffusion and adoption of IT products and processes in a Danish Bank. Paper Presented at the Diffusing Software Products and Process Innovations, IFIP TC8 WG8.1 Fourth Working Conference on Diffusing Software Products and Process Innovations, Banff, Canada, April 7-10.
40. Rogers EM. 2003. Diffusion of Innovations, 5th edn. The Free Press: New York.
41. Scherr AL. 1993. A new approach to business processes. IBM Systems Journal 32(1): 80-98.
42. Stelzer D, Mellis W. 1998. Success factors of organizational change in software process improvement. Software Process-Improvement and Practice 4(4): 227-250.
43. Walsham G. 1995. Interpretive case-studies in is research - nature and method. European Journal of Information Systems 4(2): 74-81.
44. Weick KE, Quinn RE. 1999. Organizational change and development. Annual Review of Psychology 50: 361-386.
45. Weinberg GM. 1997. Quality Software Management: Volume 4, Anticipating Change. Dorset House Publishing: New York.
46. Yin RK. 1994. Case Study Research: Design and Methods, 2nd edn. Sage Publications: Thousand Oaks, CA.
47. Zmud RW. 1984. An examination of 'Push-Pull' theory applied to process innovation in knowledge work. Management Science 30(6): 727-738.