Software Project Management Fallacies

Ana M. Moreno, Lawrence Peters


Software project management plays a critical role in software projects. Therefore, software project management actions have an important impact on software projects and organizations. However, software engineers often become software project managers with little or no training in project management. As a result, sometimes they have to rely on hearsay or their own assumptions to formulate strategies and a plan of action for managing software projects. This has led to several software project management misconceptions or fallacies that can have important negative effects on software projects. This paper examines some relevant fallacies based, on the authors’ experience and discusses published material which refutes them. This work contributes to the practice of Software Project Management by identifying and correcting practices which can reduce the success rate of software projects.


  1. APA, 2006. American Psychological Association, Multitasking: Switching costs. Research in Action, 0 March, 2006.
  2. Belbin, R., 1996. Management Teams - Why They Succeed or Fail, Butterworth Heineman, London.
  3. Boehm, B., 1981. Software Engineering Economics, Prentice-Hall, Englewood Cliffs, N.J., pp. 486-487.
  4. Cone, E., 1998. Managing that Churning Sensation, Information Week, No. 680, (May, 1998), 50-67.
  5. Cusumano, M., 2004. The Business of Software: What Every Manager, Programmer, and Entrepreneur Must Know to Thrive and Survive in Good Times and Bad, Free Press, New York, New York.
  6. Drucker, P., 2006. Managing for Results (reissue - originally published 1954), Harper Business, New York, NY.
  7. Fleming, Q. Koppelman, J., 2010. Earned Value Project Management - Fourth Edition, Project Management Institute, Newtown Square, PA.
  8. Flyvberg, B., 2006. From Nobel Prize to Project Management: Getting Risks Right, Project Management Journal, (August, 2006), pp. 5 - 15.
  9. Gardner, H.K., 2012. Performance Pressure as a Double Edged Sword: Enhancing Team Motivation While Undermining the Use of Team Knowledge, Harvard Business School, Working Paper 09-126.
  10. Garvin, D., 2013. How Google Sold Its Engineers on Management, Harvard Business Review.
  11. Gino, F., Ariely, D., 2011. The Dark Side of Creativity: Original Thinkers Can be More Dishonest, Journal of Personality and Social Psychology, Vol. 102, No. 3, 445-459.
  12. Grant, A.M., Gino F., 2010, A Little Thanks Goes a Long Way: Explaining Why Gratitude Expressions Motivate Prosocial Behavior, Journal of Personality and Social Psychology, June, Vol. 98, No. 6, 946 - 955.
  13. Gulla, J., 2012. Seven Reasons IT Projects Fail, IBM Systems Magazine, February.
  14. Herzberg, F., 1966. Work and the Nature of Man, The World Publishing Company, Cleveland, Ohio.
  15. Huckman, R., Staats, B., 2013. The Hidden Benefits of Keeping Teams Intact, Harvard Business Review, (December).
  16. Jensen, R., 2000, Don't Forget About Good Management, CrossTalk Magazine, 30.
  17. Kahneman, D., 1994. New Challenges to the Rationality Assumption, Journal of Institutional and Theoretical Economics, 150, 18-36.
  18. Katz, R., 2013 Motivating Technical Professionals Today, IEEE Engineering Management Review, Volume 41, Number 1, 28-37.
  19. Kerzner, H. R., 2013. Project Management: A Systems Approach to Planning, Scheduling and Controlling, Wiley Publishing.
  20. Lovallo, D., Kahneman, D,. 2003. Delusions of Success: How Optimism Undermines Executives' Decisions, Harvard Business Review, 56-63.
  21. Maslow, A.H., 1971, The Farther Reaches of Human Nature, Viking Press, New York, NY.
  22. Maylor, H., Turner, N. and Murray-Webster, R., 2013. How Hard Can It Be? Research-Technology Management, (July-August), 46-51.
  23. McClelland, D.C., 1961. The Achieving Society, Van Nostrand-Rheinhold, Princeton, NJ.
  24. McConnell, S., 2000. The Software Manager's Toolkit, IEEE Software, (July/August, 2013).
  25. Myers, C., Staats, B. and Gino, F., 2014. My Bad! How Internal Attribution and Ambiguity of Responsibility Affect Learning from Failure, Harvard Business School, Working Paper 14-104.
  26. Ophira, E., Nass, C., and Wagner, A. 2009. Cognitive Control in Media Multitaskers, Proceedings of the National Academy of Sciences, Vol. 106, No. 33.
  27. Ordonez, L., Schweitzer, M., Galinsky, A. and Bazerman, M., 2009. Goals Gone Wild: The Systematic Side Effects of Overprescribing Goal Setting, The Academy of Management Perspectives, February, Vol. 23, No. 1, 6-16.
  28. Peters, L. 2008. Getting Results from Software Development Teams, Microsoft Press Best Practices Series, Redmond, WA.
  29. Peters, L., Moreno, A, 2014. Educating Software Project Managers - Revisited, Conference on Software Engineering Education and Training, Florence, Italy.
  30. Peters, L., 2015. Managing Software Projects on the Edge of Chaos - From Antipatterns to Success, Software Consultants International Ltd., Auburn, WA.
  31. Rombach, D. 2003. Teaching How to Engineer Software, keynote address at the Conference on Software Engineering and Education, Madrid, Spain, March.
  32. Ryan, R. M., Deci, E. L., 2000. Intrinsic and Extrinsic Motivations: Classic Definitions and New Directions, Contemporary Educational Psychology, Volume 25, 54 - 67.
  33. Software Extension to the PMBOK Guide Fifth Edition. 2013. IEEE Computer Society.
  34. Staats, B.R., Brunner, D.J., Upton, D.M., 2011. Lean Principles, Learning, and Knowledge Work: Evidence from a Software Services Provider, Journal of Operations Management, July.
  35. Staats, B.R., Milkman, K.L. and Fox, C. R., 2014. The Team Sizing Fallacy: Underestimating The Declining Efficiency of Larger Teams, Forthcoming article in Organizational Behavior and Human Decision Processes.
  36. Staats, B.R., Gino, F., Pisano, G.P., 2010. Varied Experience, Team Familiarity, and Learning: The Mediating Role of Psychological Safety, Working Paper 10-016, (2010), Harvard Business School.
  37. Standish Group, 2015. The Standish Group. The CHAOS Report, West Yarmouth, MA, 2015.Taylor, B., 2011, Why Do Smart People Do Such Dumb Things? Harvard Business Review, (January 11, 2011).
  38. Tomer, A., 2014. Software Manageeringment Teaching Project from Software Engineer Perspective, Global Engineering Education Conference (EDUCON, 2014).
  39. Touran, A., 2003. Calculation of Contingency in Construction Projects, IEEE Transactions on Engineering Management 50(2), (May, 2003), 135- 140.
  40. Townsend, R., 1970. Up the Organization - How to Stop The Corporation from Stifling People and Strangling Profits, Alfred Knopf, New York, N.Y.
  41. Townsend, R., 1984. Further Up the Organization - How to Stop Management from Stifling People and Strangling Profits, Alfred Knopf, New York, N.Y.
  42. Weick, K., 1987. Organizational Culture as a Source of High Reliability, California Management Review, 29/2, 112-127.
  43. Weinberg, G., 1994. Quality Software Management, vol. 3: Congruent Action, New York, N.Y.: Dorset House Publishing, 15-16.

Paper Citation

in Harvard Style

Moreno A. and Peters L. (2016). Software Project Management Fallacies . In Proceedings of the 11th International Joint Conference on Software Technologies - Volume 1: ICSOFT-EA, (ICSOFT 2016) ISBN 978-989-758-194-6, pages 109-116. DOI: 10.5220/0005927001090116

in Bibtex Style

author={Ana M. Moreno and Lawrence Peters},
title={Software Project Management Fallacies},
booktitle={Proceedings of the 11th International Joint Conference on Software Technologies - Volume 1: ICSOFT-EA, (ICSOFT 2016)},

in EndNote Style

JO - Proceedings of the 11th International Joint Conference on Software Technologies - Volume 1: ICSOFT-EA, (ICSOFT 2016)
TI - Software Project Management Fallacies
SN - 978-989-758-194-6
AU - Moreno A.
AU - Peters L.
PY - 2016
SP - 109
EP - 116
DO - 10.5220/0005927001090116