Software engineering course projects: Failures and recommendations

  • Manmahesh Kantipudi
  • James S. Collofello
  • Ken W. Collier
  • Scott Medeiros
Session 11: Laboratory and Project Experiences
Part of the Lecture Notes in Computer Science book series (LNCS, volume 640)


In the past there has been much written about successful commercial software development projects while failures are largely ignored. Similarly, the software engineering education literature contains many references to successful course projects, while academic course project failures are rarely described. This paper provides an analysis of software engineering course project failures as well as practical recommendations for increasing the chances of successful projects. The failures are grouped into technical, personal and management categories. Our recommendations are based upon a synthesis of current approaches being adopted to various degrees in industry as well as our own personal experiences. Most of our non-technical recommendations have historically received very little attention in course offerings or even current popular software engineering texts. It is our goal in this paper to sensitize software engineering course instructors to the possible failures their project teams face as well as provide them with insight into increasing their teams chances for success.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. [Boehm84]
    Boehm, B.W., M.H. Penedo, E.D. Stuckle and R.D. Williams, A Software Development Environment for Improving Productivity. Computer, vol. 17, June 1984, pp. 30–42.Google Scholar
  2. [Boehm87]
    Boehm, B.W., Improving Software Productivity, Computer, vol. 20, September 1987, pp. 43–57.Google Scholar
  3. [Boehm89]
    Boehm, B.W. and R. Ross, Theory-W Software Project Management: Principles and Examples. IEEE Transactions on Software Engineering, vol. 15, no. 7, July 1989, pp. 902–916.Google Scholar
  4. [Brooks75]
    Brooks, F.P., The Mythical Man Month: Essays on Software Engineering Addison-Wesley, 1975.Google Scholar
  5. [Fagan76]
    Fagan, M.E., Design and Code Inspections to Reduce Errors in Program Development, IBM Systems Journal, vol.15, no.3, March 1976, pp.105–211.Google Scholar
  6. [Glass77]
    Glass, R. L., The Universal Elixir and Other Computing Projects Which Failed, Computing Trends, 1977, reprinted 1981.Google Scholar
  7. [Humphrey89]
    Humphrey, W., Managing the Software Process, Addison-Wesley, 1989.Google Scholar
  8. [Huszczo90]
    Huszczo, G.E., Training for Team Building, Training and Development Journal, February 1990, vol.44, pp.37–43.Google Scholar
  9. [Johnson86]
    Johnson, C.R., An Outline for Team Building, Training, January 1986, vol.23, p.48–52.Google Scholar
  10. [King88]
    King, D., Team Excellence, Management Solutions, October 1988, vol.33, pp.25–28.Google Scholar
  11. [Kistler89]
    Kistler, E.L., Managing Productivity More Effectively, Proceedings of the Second International Conference on Engineering Management: Managing Technology in a Competitive International Environment, September 10–13, 1989, pp.429–436.Google Scholar
  12. [Lawrence84]
    Lawrence, K. Motivating Staff, Data Processing, vol. 26, November 1984.Google Scholar
  13. [Maccoby89]
    Maccoby, M., Building Teamwork, Research Technology Management, November–December 1989, vol.32, pp.9–10.Google Scholar
  14. [McCreight83]
    McCreight, R.E., A Five Role System for Motivating Improved Performance, Personnel Journal, January 1983, vol.62, pp.30–32.Google Scholar
  15. [McGarvey90]
    McGarvey, R., Creative Thinking, USAIR, June 1990, pp. 34–41.Google Scholar
  16. [Owens91]
    Owens, T., The Self-Managing Work Team, Small Business Reports, vol. 16, no. 2, February 1991.Google Scholar
  17. [Raudsepp83]
    Raudsepp, E. How to Build an Effective Team, Machine Design, vol. 55, November 24, 1983.Google Scholar
  18. [Rettig90]
    Rettig, M., Software Teams, Communications of the ACM, vol. 33, no. 10, October 1990, pp. 23–27.Google Scholar
  19. [Root84]
    Root, L.J.M., IEs Should Examine Impact of Management Style on Motivation and Productivity. Industrial Engineering, vol. 16, January 1984, pp. 94–99.Google Scholar
  20. [Shea87]
    Shea, G.P. and R.A. Guzzo, Group Effectiveness: What Really Matters?, Sloan Management Review, Spring 1987, vol.28, pp.25–31Google Scholar
  21. [Stokes90]
    Stokes Jr., S.L., Building Effective Project Teams, The Journal of Information Systems Management, vol. 7, no. 3, Summer 1990, pp.38–45.Google Scholar
  22. [Tayntor85]
    Tayntor, C.B., Motivating the Maintenance Programmer, Infosystems, February 1985, vol.32, pp.97Google Scholar
  23. [Thamhain87]
    Thamhain, H.J. and D.L. Wilemon, Building High Performing Engineering Project Teams, IEEE Transactions on Engineering Management, vol. EM-34, no. 3, August 1987, pp. 130–137.Google Scholar
  24. [Thayer80]
    Thayer, R. H., Pyster A. and Wood R. C., The Challenge of Software Engineering Project Management, IEEE Computer, August 1980, pp. 51–59.Google Scholar
  25. [Thayer82]
    Thayer, R. H., Pyster A. and Wood R. C., Validating Solutions to Major Problems in Software Engineering Project Management, IEEE Computer, August 1982, pp. 65–77.Google Scholar
  26. [Thedens84]
    Thedens, M., Communication is the Key, Datamation, vol. 30, May 1984, pp.147–148.Google Scholar
  27. [Varney89]
    Varney, G.H., Building Productive Teams, San Francisco: Jossey-Bass Publishers, 1989.Google Scholar
  28. [Weisbord85]
    Weisbord, M.R., Team Effectiveness Theory, Training and Development Journal, January 1985, vol.39, pp.26–29Google Scholar
  29. [Wolff89]
    Wolff, M.F., Building Teams-What Works (Sometimes) Research Technology Management, November–December 1989, vol.32, pp.9–10Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1992

Authors and Affiliations

  • Manmahesh Kantipudi
    • 1
  • James S. Collofello
    • 1
  • Ken W. Collier
    • 1
  • Scott Medeiros
    • 1
  1. 1.Department of Computer Science and EngineeringArizona State UniversityTempe

Personalised recommendations