Managing information systems (IS) projects is a notoriously difficult task. The project manager is a crucial player in a successful IS development project. This research examines how a project manager's prior experience and risk propensity influence his or her decision making. An experiment was conducted that showed that both experience and risk propensity have significant influence on the decisions made.
AbdolmohammadiM., & WrightA. (1987). An examination of the effects of experience and task complexity on audit judgements. The Accounting Review, 62(1), 1–13.
2.
AiyerJ., RajkumarT. M., & HavelkaD. (2005). A staged framework for the recovery and rehabilitation of troubled IS development projects. Project Management Journal, 36(4), 32–43.
3.
BairdI. S., & ThomasH. (1985). Toward a contingency model of strategic risk taking. Academy of Management Review, 10, 230–243.
4.
BanduraA. (1977). Social learning theory.Englewood Cliffs, NJ: Prentice Hall.
5.
BarkiH., RivardS., & TalbotJ. (1993). Toward an assessment of software development risk. Journal of Management Information Systems, 10(2), 203–225.
6.
BazermanM. H., BeekunR. I., & SchoormanF. D. (1982). Performance evaluation in dynamic context: The impact of a prior commitment to the ratee. Journal of Applied Psychology, 67, 873–876.
7.
BettmanJ. R. (1973). Perceived risk and its components: A model and empirical test. Journal of Market Research, 10, 184–190.
8.
BroadbentM., WeillP., & St. ClairD. (1999). The implications of information technology infrastructure for business process redesign. MIS Quarterly, 23(2), 159–182.
9.
BrockhausR. H. (1980). Risk-taking propensity of entrepreneurs. Academy of Management Journal, 23, 509–520.
10.
BrocknerJ., NathansonS., FriendA., HarbeckJ., SamuelsonC., HouserR. (1984). The role of modeling processes in the “knee deep in the big muddy” phenomenon. Organizational Behavior and Human Performance, 33(1), 77–99.
11.
BrooksF. P.Jr. (1987). No silver bullet: Essence and accidents of software engineering. Computer, 20(4), 10–19.
12.
CorsiniR. J., & OsakiB. D. (Eds.). (1984). Encyclopedia of psychology (Vol. 3). New York: Wiley.
13.
DeVinneP. B. (Ed.). (1985). The American Heritage dictionary (2nd college ed.). Boston: Houghton Mifflin.
14.
FischhoffB., LichtensteinS., SlovicP., DerbyS. L., & KeeneyR. L. (1981). Acceptable risk.Cambridge, UK: Cambridge University Press.
HavelkaD., & RajkumarT. M. (2006). Using the troubled project recovery framework: Problem recognition and decision to recover. e-Service Journal, 5(1), 43–73.
21.
HochS. J., & LoewensteinG. F. (1989). Outcome feedback: Hindsight and information. Journal of Experimental Psychology: Learning, Memory, and Cognition, 15, 605–619.
22.
HuffR. A., KeilM., KappelmanL. A., & PrybutokV. R. (1997). Validation of the Sitkin-Weingart business risk propensity scale. Management Research News, 20(12), 39–48.
23.
IacovouC. L., & DexterA. S. (2004). Turning around runaway information technology projects. California Management Review, 46(4), 68–88.
24.
IansitiM. (2000). How the incumbent can win: Managing technological transitions in the semiconductor industry. Management Science, 46(2), 169–185.
25.
JeffreyC. (1992). The relation of judgement, personal involvement, and experience in the audit of bank loans. The Accounting Review, 67, 802–819.
26.
KahnemanD., & TverskyA. (1979). Prospect theory: An analysis of decisions under risk. Econometrica, 47, 263–291.
27.
KeilM., & MixonR. (1994). Understanding runaway IT projects: Preliminary results from a program of research based on escalation theory. In NunamakerJ. F.Jr., & SpragueR. H.Jr., (Eds.), Proceedings of the twenty-seventh annual Hawaii International Conference on Systems Sciences (Vol. 3, pp. 469–478). Los Alamitos, CA: IEEE Computer Society Press.
28.
KeilM., MixonR., SaarinenT., & TuunainenV. (1994/95). Understanding runaway information technology projects: Results from an international research program based on escalation theory. Journal of Management Information Systems, 11(3), 65–85.
29.
KeilM., & RobeyD. (1999). Turning around troubled software projects: An exploratory study of the deescalation of commitment to failing courses of action. Journal of Management Information Systems, 15(4), 63–87.
30.
KeilM., TruexD. P.III, & MixonR. (1995). The effects of sunk costs and project escalation on information technology project escalation. IEEE Transactions on Engineering Management, 42(4), 1–10.
31.
KindelS. (1992, March 31). The computer that ate the company. Financial World, 161, 96–98.
32.
KoganN., & WallachM. A. (1964). Risk taking: A study in cognition and personality.New York: Holt, Rinehart & Winston.
33.
LevineH. G., & RossmooreD. (1993). Diagnosing the human threats to information technology implementation: A missing factor in systems analysis illustrated in a case study. Journal of Management Information Systems, 10(2), 55–73.
34.
LibbyR. (1995). The role of knowledge and memory in audit judgement. In AshtonR. H., & AshtonA. H. (Eds.), Judgement and decision-making research in accounting and auditing (pp. 176–206). New York: Cambridge University Press.
35.
MarchJ. G., & ShapiraZ. (1987). Managerial perspectives on risk and risk-taking. Management Science, 33, 1404–1418.
36.
MarchewkaJ. T., & KeilM. (1995). Portfolio theory approach for selecting and managing IT projects. Information Resources Management Journal, 8(4), 5–14.
37.
McFarlanW. (1981). Portfolio approach information systems. Harvard Business Review, 59(5), 142–151.
38.
NealeM. A., BazermanM. H., NorthcraftG. B., & AlpersonC. (1986, March). “Choice shift” effects in group decisions: A decision bias perspective. International Journal of Small Group Research, pp. 33–42.
39.
NewmanM., & SabherwalR. (1991). Information system development: Four process scenarios with case studies. Journal of Information Systems, 5(1), 84–101.
40.
RichardsR. M., PrybutokV. R., & KappelmanL. A. (1996). Influence of computer user training on decision-making risk preferences. Management Research News, 19(11), 26–41.
41.
RoweW. D. (1977). An anatomy of risk.New York: Wiley.
SinghJ.V. (1986). Performance, slack, and risk taking in organizational decision making. Academy of Management Journal, 29, 562–585.
44.
SitkinS. B., & PabloA. L. (1992). Reconceptualizing the determinants of risk behavior. Academy of Management Review, 17(1), 9–39.
45.
SitkinS. B., & WeingartL. R. (1995). Determinants of risky decision-making behavior: A test of the mediating role of risk perceptions and propensity. Academy of Management Journal, 38, 1573–1592.
StawB. M., & RossJ. (1987). Behavior in escalation situations: Antecedents, prototypes, and solutions. In CummingsL. L., & StawB. M. (Eds.), Research in organizational behavior (Vol. 9, pp. 39–78). Greenwich, CT: JAI Press.
48.
SutherlandS. (Ed.). (1989). International dictionary of psychology.New York: Continuum.
49.
ThayerR. H., PysterA. B., & WoodR. C. (1981). Major issues in software engineering project management. IEEE Transactions on Software Engineering, 7, 333–342.
50.
TubbsR. M. (1992). The effect of experience on the auditor's organization and amount of knowledge. The Accounting Review, 67, 783–801.
51.
TverskyA., & KahnemanD. (1986). Rational choice and the framing of decisions. In HogarthR. M., & RederM. W. (Eds.), Rational choice: The contrast between economics and psycholo-gy (pp. 67–94). Chicago: University of Chicago Press.
52.
TverskyA., & KahnemanD. (1992). Advances in prospect theory: Cumulative representation of uncertainty. Journal of Risk and Uncertainty, 5, 297–323.
53.
WicklundR.A., & BrehmJ.W. (1976). Perspectives on cognitive dissonance.Hillsdale, NJ: Erlbaum.
54.
WolmanB. B. (Ed.). (1989). Dictionary of behavioral science.San Diego, CA: Academic Press.
ZmudR. W., McLaughlinC. P., & MightR. J. (1984). An empirical analysis of project management technique implementation success. In SchutzR. L., & GinsbergM. J. (Eds.), Management science implementation applications of management science: Supplement 1 (pp. 107–132). Greenwich, CT: JAI Press.
