This Article 
 Bibliographic References 
 Add to: 
Improving Speed and Productivity of Software Development: A Global Survey of Software Developers
December 1996 (vol. 22 no. 12)
pp. 875-885

Abstract—Time is an essential measure of performance in software development because time delays tend to fall directly to the bottom line. To address this issue, this research seeks to distinguish time-based software development practices: those managerial actions that result in faster development speed and higher productivity. This study is based upon a survey of software management practices in Western Europe and builds upon an earlier study we carried out in the United States and Japan. We measure the extent to which managers in the United States, Japan, and Europe differ in their management of software projects and also determine the tools, technology, and practices that separate fast and slow developers in Western Europe.

[1] M. Van Genuchten, "Why is Software Late? An Empirical Study of Reasons for Delay in Software Development," IEEE Trans. Software Eng., vol. 17, no. 6, pp. 582-590, 1991.
[2] G.P. Zachary, "How Ashton-Tate Lost Its Leadership in PC Software Arena," The Wall Street J., Apr.10, 1990.
[3] B. Zeigler, "New IBM PCs Are Superfast, but Might Be Too Late," Wall Street J., June16, 1995.
[4] J.D. Blackburn, Time-Based Competition: The Next Battle Ground in American Manufacturing.Homewood, Ill.: Business One Irwin, 1991.
[5] G. Stalk and T. Hout, Competing Against Time,New York: Free Press, 1990.
[6] P. Smith and D. Reinertsen, Developing Products in Half the Time.New York: Van Nostrand Reinhold, 1991.
[7] B. Curtis, H. Krasner, and N. Iscoe, "A Field Study of the Software Design Process for Large Systems," Comm. ACM, vol. 31, no. 11, pp. 1,268-1,287, 1988.
[8] K. Maxwell, L. Van Wassenhove, and S. Dutta, "Software Development Productivity of European Space, Military and Industrial Applications," IEEE Trans. Software Eng., Oct. 1996.
[9] J. Blackburn, G. Scudder, L. Van Wassenhove, and C. Hill, "Time-Based Software Development," Integrated Manufacturing Systems, vol. 7, no. 2, 1996.
[10] J. Blackburn, S. Baylor, and G. Scudder, "Software Development in Japan: Some Preliminary Findings," Working Paper #92-57, Vanderbilt Univ., Owen Graduate School of Management, Sept. 1992.
[11] G. Scudder and C. Hill, "Software Development in Japan: Some Findings from Some Major Companies," Vanderbilt Univ., Owen Graduate School of Management Working Paper #93-60, Aug. 1993.
[12] J. Blackburn, G. Hoedemaker, and L. Van Wassenhove, "Interviews with Product Development Managers," Working Paper #92-56, Vanderbilt Univ., Owen Graduate School of Management, 1992.
[13] F.P. Brooks, Jr., The Mythical Man-Month: Essays on Software Engineering, Addison Wesley Longman, Reading, Mass., 1975.
[14] R. Yeh, "Notes on Concurrent Engineering," IEEE Trans. Knowledge and Data Eng., vol. 4, no. 5, pp. 407-414, 1992.
[15] S. Siegel and N.J. Castellan Jr., Nonparametric Statistics for the Behavioral Sciences,New York: McGraw-Hill, pp. 291-298, 1988.
[16] C. Jones, Assessment and Control of Software Risks, Yourdon Press, Englewood Cliffs, N.J., 1994.
[17] L.H. Putnam and W. Myers, Measures for Excellence: Reliable Software on Time, Within Budget, Yourdon Press, Englewood Cliffs, N.J., 1992.
[18] S. McConnell, Code Complete: A Practical Handbook of Software Construction. Microsoft Press, 1993.

Index Terms:
Software engineering, software development, global performance comparisons, software speed and productivity, management factors, empirical research, Europe, Japan, and the United States.
Joseph D. Blackburn, Gary D. Scudder, Luk N. Van Wassenhove, "Improving Speed and Productivity of Software Development: A Global Survey of Software Developers," IEEE Transactions on Software Engineering, vol. 22, no. 12, pp. 875-885, Dec. 1996, doi:10.1109/32.553636
Usage of this product signifies your acceptance of the Terms of Use.