Initial effects of software process improvement on an experienced software development team

Proceedings of the Annual Hawaii International Conference on System Sciences

Volumn 1, Issue , 1996, Pages 713-721

  McGuire, Eugene G ^a  

^a AMERICAN UNIVERSITY   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

HUMAN RESOURCE MANAGEMENT;

CAPABILITY MATURITY MODELS; DEVELOPMENT AND TESTING; DEVELOPMENT ENVIRONMENT; RESISTANCE TO CHANGE; SOFTWARE DEVELOPMENT TEAMS; SOFTWARE ENGINEERING INSTITUTES; SOFTWARE PROCESS IMPROVEMENT; TRAINING SESSIONS;

SOFTWARE DESIGN;

EID: 84878193429     PISSN: 15301605     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/HICSS.1996.495525     Document Type: Conference Paper

References (54)

1. Bate, R., Garcia, S., et a1 (1994). A systems engineering capability maturity model, version 1.0, Software Engineering Institute, Pittsburgh, PA.
2. Bell, R. & Bumham, J. (1991). Managing change and productivity, South-Western, Cincinnati.
3. Boehm, B. (1988). "Aspiral model of sohare development and enhancement," IEEE Computer, May, pp. 61-72.
4. Campbell, J. & Campbell, R. (1988). Productivity in organizations, Josey-Bass, San Francisco.
5. Constantine, L.L. (1995). Constantine on peopleware. Yourdon Press, Englewood Cliffs, NJ.
6. Constantine, L.L. (1993). "Work organization: Paradigms for project management and organization," Communicationsof the ACM, Vol. 36, No. 10, October 1993, pp. 35-43.
7. Cougar, J.D. & Zawicki, R.W. (1978). "Whatmotivates DP professionals," Datamation, September 1978, pp, 116-123.
8. Cougar, J.D. & Zawicki, R.W. (1980). Motivation and management of computer personnel, NY: Wiley.
9. Cougar, J.D. (1990). "Motivating analysts and programmers,"Compurenuorld, January 15, 1990, pp. 73-76.
10. [lo] Curtis, B., Hefley, W.E., & Miller, S. (1995). People capability maturity model draft version 0.3, Software Engineering Institute, Pittsburgh, PA.
11. [ll] Curtis, B. & Paulk, M. (1993). "Creating a software process improvement program," Znformation and Sofhvare Technology, Vol. 35, No. 6, JuneIJuly 1993, pp. 381-386.
12. Daskalantonakis, M. (1994). "Achieving higher SEI levels," IEEE Computer, July 1994, pp. 17-24.
13. Davis, A.M. (1994). "Fifteen principles of software engineering,"IEEESoffware, November 1994, pp. 94-96, 101.
14. Demarco, T. & Lister, T. (1987). Peopleware; Productive projects and team. Dorsett House Publishing, NY.
15. Fanvell, D.W., Kuramoto, L., Lee, D., Trauth, E.M., & Winslow, C. (1992). "Anew paradigm for IS: The educational implications," Journal of Informution Systems Management, Spring 1992, pp. 7-14.
16. Finkelstein, A. (1992). "A software process immaturity model," ACM SIGSOFT, October 1992, PP.22-23.
17. Glass, R. L. (1995). SofhYare creativity. Prentice-Hall, Englewood Cliffs, NJ .
18. Gulden, G.K. & Reck, R.H. (1992). "Combining quality and reengineering efforts for process excellence," Information Strategy: The Executive's Journal, Spring 1992, pp. 10-16.
19. 1191 Guterl, F. (1984). "Design case history: Apple's Macintosh," IEEE Spectrum, Vol. 21, No. 12, December, pp. 34-44.
20. Guzzo, R.A., Salas, E., et a1 (1995). Team efectiveness and decision making in organizations, Jossey-Bass, CA
21. Hare], D. (1992). "Biting the silver bullet: Toward a brighter future for system development," IEEE Computer, January 1992, PP. 8-20.
22. Holtzblatt, K. & Beyer, H. (1993). "Making customer-centered design work for teams," Communications of the ACM, Vol. 36, No. 10, October 1993, pp. 93-103.
23. Humphrey, W. (1987). Managingfor innovation:Leading technicalpeople. PrenticeHall, Englewood Cliffs, NJ.
24. Humphrey, W. (1989). Managing the sofiare process. Addison-Wesley, Reading, MA.
25. Humphrey, W., Snyder, T.R., Willis, R.R. (1991). "Software process improvement at Hughes Aircraft," IEEE Sofhuare, July 1991, pp. 11-23.
26. Hutchings, T., Hyde, M.G., Marca, D. & Cohen, L. (1993). "Process improvement that lasts: An integrated training and consultingmethod," Communicationsof the ACM, Vol. 36, No. 10, October 1993, pp. 105-113.
27. [27l Hyman, R.B. (1993). "Creativechaos in high-performance teams: An experience report," Communications of the ACM, Vol. 36, No. 10, October 1993, pp. 57-60.
28. Igbaria, M., Parasuraman, S., & Badawy, M.K. (1994). "Work experiences, job involvement, and quality of work life among information systems personnel," MIS Quarterly, June 1994, pp. 175-201.
29. Jones, D.W. (1995a). "Repeatablesoftwaredevelopment, part I: Quality Assurance," Sofhuare Development, Vol. 3, No. 5, May 1995, pp. 59-61.
30. Jones, D.W. (1995b). "Repeatablesoftware development, part 11: Configurationand requirements management," Software Development, Vol. 3, No. 6, June 1995, pp. 55-57.
31. Jones, D.W. (1995)."Repeatablesoftware development, part 111: Software management, Sofhuare Development, Vol. 3, NO. 7, July 1995, pp. 47-51.
32. Khajenoori, S. (1994). "Process-oriented software education," IEEE Sofhyare, November 1994, pp. 99-101.
33. Kidder, T. (1981). The Soul of a New Machine, Little, Brown, and Company: Boston, MA.
34. Kim, K.K. & Umanath, N.S. (1993). "Structure and perceivedeffectivenessof softwaredevelopmentsubunits:Atask contingency analysis," Journal of Management Information Systems, Vol. 9, No. 3, pp. 157-181.
35. Kopelman, R. (1986). Managing productivity in organizations, McGraw-Hill, New York.
36. Kraut, R.E. & Streeter, L.A. (1995). "Coordination in software development," Communicationsof the ACM, Vol. 38, No. 3, March 1995, pp. 69-81.
37. McIntyre, S.C. (1992). "Overcomingad hoc development: EnablinglDisabling factors in software quality maturation," Proceedings of the 25th Hawaii International Conference on Systems Sciences, IEEE Computer Society Press, Vol IV, January 1992, pp. 624-633.
38. McIntyre, S.C. (1994). "Organizational issues underlie software quality," Proceedings of the 27th Annual Hawaii International Conference on System Sciences, IEEE Computer Society Press, January 1994, pp. 820-821.
39. Myers, W. (1994). "Hard data will lead managers to quality," IEEE Sofhuare, March 1994, pp. 100-101.
40. Niederman,F.,Brancheau,J.C., &Wetherbe, J.C. (1991). "Information systems management issues for the 1990s," MIS Quarterly, December 1991, pp. 475-500.
41. Paulk, M., Curtis, Chrisis, M.B., &Weber, C.V. (1993). "CapabilityMaturity Model, Version 1.1,I' IEEE Software, July 1993, pp. 18-27.
42. Pierce, K.R. (1993). "Rethinkingacademia's conventional wisdom," IEEE Sofiware, March 1993, pp. 94-95, 99.
43. Pressman, R.S. (1995). "A people-centered approach to Softwareprocess improvement,"SoftwareProcess Improvement Forum, Vol. 2, No. 2, MarchlApril 1995, pp. 8-12.
44. Rasch, R.A. & Tosi, H.L. (1992). "Factors affecting sobare developers' performance: An integrated approach," MIS Quarterly, September 1992, pp. 395-409.
45. Rettig, M. & Simons, G. (1993). "A project planning and development process for small teams," Communicationsof the ACM, Vol. 36, No. 10, October 1993, pp. 45-55.
46. Royce, W.W. (1970). "Managingthe development of large software systems: Concepts and techniques," Proceedings of WESTCON,California. (Also available in Proceedings of ICSE 9. Los Alamitos, California: IEEE Computer Society.)
47. [47l Saiedian, H. &Kuzara, R. (1995). "SEI capability maturity model's impact on contractors," IEEE Computer, January 1995, pp. 16-26.
48. Srinivasan, A. & Kaier, K. (1987). "Relationshipsbetween selected organizational factors and systems development," Communications of the ACM, Vol. 30, pp. 556-562.
49. 1491 Statz, J .A.(1994). "Training effective project managers," American Programmer, Vol. 7, No. 6.
50. [SO] Thompson, K. & McParland, P. (1993). "Softwareprocess maturity (SPM) and the information systems developer," InformationandSofiare Technology, Vol. 35, No. 6, June/July 1993, pp. 331-338.
51. [Sl] Walz, D.B., Elam, J.J., & Curtis, B. (1993). "Inside a software design team: Knowledge acquisition sharing and integration," Communicationsof the ACM, Vol. 36, No. 10, October 1993, pp. 63-77.
52. Werther, W., Ruch, W., & McClure, L. (1986). Productivity throughpeople, West, St. Paul, MN.
53. Zahniser, R.A. (1993). "Design by walking around," Communications of the ACM, Vol. 36, No. 10,October 1993, pp. 115-123.
54. Zultner, R.E. (1993). "TQM for technical teams," Communications of the ACM, Vol. 36, No. 10, October 1993, pp. 79-91.