Can the outside-view approach improve planning decisions in software development projects?

Information Systems Journal

Volumn 26, Issue 4, 2016, Pages 395-418

  Shmueli, Ofira ^a   Pliskin, Nava ^a   Fink, Lior ^a  

^a BEN GURION UNIVERSITY OF THE NEGEV   (Israel)

Author keywords

experiment; inside view; outside view; over requirement; planning decisions; planning fallacy; reference information; role perspective; scope overload; software development; time underestimation

Indexed keywords

BEHAVIORAL RESEARCH; DECISION THEORY; EXPERIMENTS; SOFTWARE ENGINEERING;

INSIDE VIEW; OUTSIDE VIEW; OVER-REQUIREMENT; REFERENCE INFORMATION; ROLE PERSPECTIVE; SCOPE OVERLOAD; TIME UNDERESTIMATION;

SOFTWARE DESIGN;

EID: 84945971918     PISSN: 13501917     EISSN: 13652575     Source Type: Journal    
DOI: 10.1111/isj.12091     Document Type: Article

References (85)

1. Andres, H.P. (2001) A contingency approach to software project coordination. Journal of Management Information Systems, 18, 41–70.
2. Baccarini, D., Salm, G. & Love, P. (2004) Management of risks in information technology projects. Industrial Management and Data Systems, 104, 286–295.
3. Bajaj, N., Tyagi, A. & Agarwal, R. (2006) Software estimation: a fuzzy approach. ACM SIGSOFT Software Engineering Notes, 31, 1–5.
4. Barki, H., Rivard, S. & Talbot, J. (1993) Toward an assessment of software development risk. Journal of Management Information Systems, 10, 203–225.
5. Battles, B.E., Mark, D. & Ryan, C. (1996) An open letter to CEOs: how otherwise good managers spend too much on information technology. The McKinsey Quarterly, 1996, 116–127.
6. Bernstein, L. (2012) Things I learned from taming software development. ACM SIGSOFT Software Engineering Notes, 37, 5–6.
7. Bjarnason, E., Wnuk, K. & Regnell, B. (2010) Overscoping: reasons and consequences—a case study on decision making in software product management.4th International Workshop on Software Product Management (IWSPM), Sydney, NSW, Australia, September 27.
8. Bjarnason, E., Wnuk, K. & Regnell, B. (2012) Are you biting off more than you can chew? A case study on causes and effects of overscoping in large-scale software engineering. Information and Software Technology, 54, 1107–1124.
9. Boehm, B. & Papaccio, P. (1988) Understanding and controlling software costs. IEEE Transactions on Software Engineering, 14, 1462–1477.
10. Boehm, B. (1991) Software risk management: principles and practices. IEEE Software, 8, 32–41.
11. Boehm, B. (1999) Making RAD work for your project. Computer, 32, 113–117.
12. Boehm, B. (2000) The art of expectations management. Computer, 33, 122–124.
13. Boehm, B., Port, D. & Al-Said, M. (2000) Avoiding the software model-clash spiderweb. Computer, 33, 120–122.
14. Boehm, B. & Valerdi, R. (2008) Achievements and challenges in COCOMO-based software resource estimation. IEEE Software, 25, 74–83.
15. Boehm, B. & Lane, J.A. (2010) Evidence-based software processes. International Conference on Software Process (ICSP), Paderborn, Germany, July 8–9.
16. Buehler, R., Griffin, D. & Ross, M. (1994) Exploring the “Planning Fallacy”: why people underestimate their task completion times. J. Pers. Soc. Psychol., 67, 366–381.
17. Buehler, R., Griffin, D. & Ross, M. (1995) It's about time: optimistic predictions in work and love. European Review of Social Psychology, 6, 1–32.
18. Buehler, R., Griffin, D. & Peetz, J. (2010a) The Planning Fallacy: cognitive, motivational, and social origins. Advances in Experimental Social Psychology, 43, 1–62.
19. Buehler, R., Peetz, J. & Griffin, D. (2010b) Finishing on time: when do predictions influence completion times? Organ. Behav. Hum. Decis. Process., 111, 23–32.
20. Buehler, R., Griffin, D., Lam, K. & Deslauriers, J. (2012) Perspectives on prediction: does third-person imagery improve task completion estimates? Organ. Behav. Hum. Decis. Process., 117, 138–149.
21. Buschmann, F. (2009) Learning from failure, part 1: scoping and requirements woes. IEEE Software, 26, 68–69.
22. Buschmann, F. (2010) Learning from failure, part 2: featuritis, performitis, and other diseases. IEEE Software, 27, 10–11.
23. Charette, R.N. (2005) Why software fails. IEEE Spectrum, 42, 42–49.
24. Coman, A. & Ronen, B. (2009) Overdosed management: how excess of excellence begets failure. Human Systems Management, 28, 93–99.
25. Coman, A. & Ronen, B. (2010) Icarus' predicament: managing the pathologies of overspecification and overdesign. International Journal of Project Management, 28, 237–244.
26. Connolly, T. & Dean, D. (1997) Decomposed versus holistic estimates of effort required for software writing tasks. Management Science, 43, 1029–1045.
27. Cule, P., Schmidt, R., Lyytinen, K. & Keil, M. (2000) Strategies for heading off IS project failure. Information Systems Management, 17, 65–73.
28. Dominus, M. (2006) Creeping featurism and the ratchet effect. The Universe of Discourse, May 15 (available at http://blog.plover.com/prog/featurism.html; accessed December 15, 2014).
29. Elliott, B. (2007) Anything is possible: managing feature creep in an innovation rich environment. Proceedings of the IEEE International Engineering Management Conference, Piscataway, NJ, July 29–Aug 1.
30. Flyvbjerg, B. (2006) From Nobel prize to project management: getting risks right. Project Management Journal, 37, 5–15.
31. Flyvbjerg, B. & Budzier, A. (2011) Why your IT project may be riskier than you think. Harv. Bus. Rev., 89, 23–25.
32. Flyvbjerg, B. (2013) Quality control and due diligence in project management: getting decisions right by taking the outside view. International Journal of Project Management, 31, 760–774.
33. Gary, M. (2009) Poor industry consultancy threatens data center constructions, December 16 (available at http://www.businesscomputingworld.co.uk/poor-industry-consultancy-threatens-data-centre-constructions/; accessed December 8, 2014).
34. Goes, P.B. (2013) Editor's comments: information systems research and behavioral economics. MIS Quarterly, 37, iii–viii.
35. Gray, A.R., MacDonell, S.G. & Shepperd, M.J. (1999) Factors systematically associated with errors in subjective estimates of software development effort: the stability of expert judgment. Proceedings of the Sixth International Software Metrics Symposium, Boca Raton, FL, November 4–6.
36. Griffin, D. & Buehler, R. (2005) Biases and fallacies, memories and predictions: comment on Roy, Christenfeld, and McKenzie (2005). Psychol. Bull., 131, 757–760.
37. Halkjelsvik, T. & Jørgensen, M. (2012) From origami to software development: a review of studies on judgment-based predictions of performance time. Psychol. Bull., 138, 238–271.
38. Hayes-Roth, B. & Hayes-Roth, F. (1979) A cognitive model of planning. Cognit. Sci., 3, 275–310.
39. Heemstra, F.J. & Kusters, R.J. (1991) Function point analysis: evaluation of a software cost estimation model. European Journal of Information Systems, 1, 229–237.
40. Hill, J., Thomas, L.C. & Allen, D.E. (2000) Experts' estimates of task durations in software development projects. International Journal of Project Management, 18, 13–21.
41. Houston, D.X., Mackulak, G.T. & Collofello, J.S. (2001) Stochastic simulation of risk factor potential effects for software development risk management. Journal of Systems & Software, 59, 247–257.
42. Jones, C. (2007) Estimating Software Costs: Bringing Realism to Estimating, 2nd edn. McGraw-Hill, NY.
43. Jones, E.E. & Nisbett, R.E. (1971) The Actor and the Observer: Divergent Perceptions of the Causes of Behavior. General Learning Press, Morristown, NJ.
44. Jørgensen, M. (2004) Top-down and bottom-up expert estimation of software development effort. Information and Software Technology, 46, 3–16.
45. Jørgensen, M. & Moløkken-Østvold, K. (2004) Reasons for software effort estimation error: impact of respondent role, information collection approach, and data analysis method. IEEE Transactions on Software Engineering, 30, 993–1007.
46. Jørgensen, M. & Sjøberg, D.I.K. (2004) The impact of customer expectation on software development effort estimates. International Journal of Project Management, 22, 317–325.
47. Jørgensen, M. & Grimstad, S. (2008) Avoiding irrelevant and misleading information when estimating development effort. IEEE Software, 25, 78–83.
48. Kahneman, D. & Tversky, A. (1979) Intuitive prediction: biases and corrective procedures. TIMS Studies in Management Science, 12, 313–327.
49. Kahneman, D. & Lovallo, D. (1993) Timid choices and bold forecasts—a cognitive perspective on risk taking. Management science, 39, 17–31.
50. Kahneman, D. (2011) Thinking, Fast and Slow. Allen Lane, London, UK.
51. Kaur, K., Jyoti, B. & Rani, R. (2013) Analysis of Gold Plating: a software development risk. International Journal of Computer Science and Communication Engineering, 2, 51–54.
52. Kautz, K. (2009) The impact of pricing and opportunistic behavior on information systems development. Journal of Information Technology Theory and Application, 10, 24–41.
53. Keil, M., Tan, B., Kwok-Kee, W. & Saarinen, T. (2000) A cross-cultural study on escalation of commitment behavior in software projects. MIS Quarterly, 24, 299–325.
54. Keil, M., Im, G.P. & Mähring, M. (2007) Reporting bad news on software projects: the effects of culturally constituted views of face-saving. Information Systems Journal, 17, 59–87.
55. Khanfar, K., Elzamly, A., Al-Ahmad, W., El-Qawasmeh, E., Alsamara, K. & Abuleil, S. (2008) Managing software project risks with the chi-square technique. International Management Review, 4, 18–29.
56. Khatri, V., Vessey, I., Ramesh, V., Clay, P. & Park, S.J. (2006) Understanding conceptual schemas: exploring the role of application and IS domain knowledge. Information Systems Research, 17, 81–102.
57. Kutsch, E., Maylor, H., Weyer, B. & Lupson, J. (2011) Performers, trackers, lemmings and the lost: sustained false optimism in forecasting project outcomes—evidence from a quasi-experiment. International Journal of Project Management, 29, 1070–1081.
58. Legoux, R., Leger, P., Robert, J. & Boyer, M. (2014) Confirmation biases in the financial analysis of IT investments. Journal of the Association for Information Systems, 15, 33–52.
59. Lovallo, D. & Kahneman, D. (2003) Delusions of success: how optimism undermines executives' decisions. Harv. Bus. Rev., 81, 56–63.
60. Malhotra, N., Bhardwaj, M. & Kaur, R. (2012) Estimating the effects of Gold Plating using fuzzy cognitive maps. International Journal of Computer Science and Information Technologies, 3, 4806–4808.
61. Markus, M.L. & Keil, M. (1994) If we build it, they will come: designing information systems that people want to use. Sloan Manage. Rev., 35, 11–25.
62. McFarlan, F.W. (1981) Portfolio approach to information systems. Harv. Bus. Rev., 59, 142–150.
63. Myers, W. (1999) Early communication key to software project success. Computer, 32, 110-111.
64. Nelson, R. (2007) IT project management: infamous failures, classic mistakes, and best practices. MIS Quarterly Executive, 6, 67–78.
65. Nouri, P., Jamali, B. & Ghasemi, E. (2012) The role of experience on techno-entrepreneurs' decision making biases. Management Science Letters, 2, 1957–1964.
66. Pass, S. & Ronen, B. (2014) Reducing the software value gap. Communications of the ACM, 57, 80–87.
67. Pezzo, S.P., Pezzo, M.V. & Stone, E.R. (2006a) The social implications of planning: how public predictions bias future plans. Journal of Experimental Social Psychology, 42, 221–227.
68. Pezzo, M.V., Litman, J.A. & Pezzo, S.P. (2006b) On the distinction between yuppies and hippies: individual differences in prediction biases for planning future tasks. Personality and Individual Differences, 41, 1359–1371.
69. Ronen, B. & Pass, S. (2008) Focused Operations Management: Achieving More with Existing Resources. John Wiley & Sons, Hoboken, NJ.
70. Ropponen, J. & Lyytinen, K. (2000) Components of software development risk: how to address them? A project manager survey. IEEE Transactions on Software Engineering, 26, 98–112.
71. Rust, R.T., Thompson, D.V. & Hamilton, R.W. (2006) Defeating feature fatigue. Harv. Bus. Rev., 84, 98–107.
72. Sanna, L.J., Parks, C.D., Chang, E.C. & Carter, S.E. (2005) The hourglass is half full or half empty: temporal framing and the group Planning Fallacy. Group Dynamics: Theory, Research and Practice, 9, 173–188.
73. Sauer, C., Gemino, A. & Reich, B.H. (2007) The impact of size and volatility on IT project performance. Communications of the ACM, 50, 79–84.
74. Schmidt, R., Lyytinen, K., Keil, M. & Cule, P. (2001) Identifying software project risks: an international Delphi study. Journal of Management Information Systems, 17, 5–36.
75. Shepherd, D.A., Zacharakis, A. & Baron, R.A. (2003) VCs' decision processes: evidence suggesting more experience may not always be better. Journal of Business Venturing, 18, 381–401.
76. Slovic, P., Fischhoff, B. & Lichtenstein, S. (1977) Behavioral decision theory. Annu. Rev. Psychol., 28, 1–39.
77. Umapathy, K., Purao, S. & Barton, R.R. (2008) Designing enterprise integration solutions: effectively. European Journal of Information Systems, 17, 518–527.
78. Weick, M. & Guinote, A. (2010) How long will it take? Power biases time predictions. Journal of Experimental Social Psychology, 46, 595–604.
79. Westfall, L. (2005) The what, why, who, when and how of software requirements.Proceedings of the ASQ World Conference on Quality and Improvement, Seattle, WA, May 16–18.
80. Wetherbe, J.C. (1991) Executive information requirements: getting it right. MIS Quarterly, 15, 51–65.
81. Wheatcraft, L.S. (2011) Triple your chances of project success risk and requirements. INCOSE International Symposium, Denver, CO, June 23.
82. Williams, L., Kessler, R.R., Cunningham, W. & Jeffries, R. (2000) Strengthening the case for pair programming. IEEE Software, 17, 19–25.
83. Yang, D., Boehm, B., Yang, Y., Wang, Q. & Li, M. (2007) Coping with the cone of uncertainty: an empirical study of the SAIV process model. In: Software Process Dynamics and Agility, pp. 37–48, Springer, Berlin, Germany.
84. Zmud, R. (1980) Management of large software efforts. MIS Quarterly, 4, 45–55.
85. Zwikael, O. & Smyrk, J. (2011) An engineering approach for project scoping.IEEE 18th International Conference on Industrial Engineering and Engineering Management, Changchun, China, September 3–5.