Project failure in information sytems development continues to plague organizations. A lack of intrinsic and extrinsic rewards for developers may be a cause of such failure. A survey instrument was created using existing project success scales and items based on structured interviews with 12 IS project managers. Two hundred two members of the Project Management Institute completed the survey. After rigorous validation, path analysis (an extension of multiple regression that simultaneously tests more complex relationships) showed that use of intrinsic rewards predicted client satisfaction and perceived quality (but not on-time and within-budget implementation success), whereas use of extrinsic rewards predicted implementation success (but not satisfaction or quality). Future researchers might investigate reasons for these complementary findings. Managers might use the findings in efforts to improve information systems project success.
AndersonE. S. (2003). Understanding your project organization's character. Project Management Journal34(4), 4–11.
2.
AndersonJ. C. (1987). An approach for confirmatory measurement and structural equation modeling of organizational properties. Management Science33(4), 525–541.
3.
AndersonJ. C., & GerbingD. W. (1988). Structural equation modeling in practice: A review and recommended two-step approach. Psychological Bulletin103(3), 411–423.
4.
ArainF. M. (2005). Strategic management of variation orders for institutional buildings: Leveraging on information technology. Project Management Journal36(4), 66–77.
5.
ArmstrongJ. S., & OvertonT. S. (1977). Estimating Nonresponse Bias in Mail Surveys. Journal of Marketing Research14, 396–402.
6.
AryaA., GloverJ., & RoutledgeB. R. (2002). Project assignment rights and incentives for eliciting ideas. Management Science48(7), 886–899.
7.
AustinR. D. (2001). The effects of time pressure on quality in software development: An agency model. Information Systems Research12(2), 195–207.
8.
BagozziR. P. (1981). Evaluating structural equation models with unobservable variables and measurement error: A comment. Journal of Marketing Research18(August), 375–381.
9.
BaileyJ. E., and PearsonS. W. (1983). Development of a tool for measuring and analyzing computer user satisfaction. Management Science29(5), 530–545.
10.
BakerB., & MenonR. (1995). Politics and project performance: The fourth dimension of project management. PM Network, November, 16-21.
BakerG. P., JensenM. C., & MurphyK. J. (1988). Compensation and incentives: Practice versus theory. Journal of Finance43(3), 593–616.
13.
BankerR. D., LeeS.-Y., PotterG., & SrinivasanD. (1996). Contextual analysis of performance impacts of outcome-based incentive compensation. Academy of Management Journal39(4), 920–948.
14.
Bassett-JonesN., & LloydG. C. (2005). Does Herzberg's motivation theory have staying power?The Journal of Management Development24(10), 929–943.
15.
BeardenW. O., NetemeyerR. G., & TeelJ. E. (1989). Measurement of consumer susceptibility to interpersonal influence. Journal of Consumer Research15(March), 472–480.
16.
BenabouR., & TiroleJ. (2003). Intrinsic and extrinsic motivation. The Review of Economic Studies70(244), 489–520.
17.
BenningtonP., & BaccariniD. (2004). Project benefits management in IT projects: An Australian perspective. Project Management Journal35(2), 20–30.
18.
BentlerP. M. (1989). EQS: Structural Equations Program Manual.Los Angeles, CA: BMDP Statistical Software, Inc.
19.
ByrneB. M. (1994). Structural Equation Modeling with EQS and EQS/Windows: Basic Concepts, Applications, and Programming.London: Sage.
20.
CafassoR. (1994). Few IS projects come in on time, on budget. Computerworld28(50), 20.
21.
CagnoE., Di GiulioA., & TruccoP. (2004). State-of-art and development prospects of E-procurement in the Italian engineering & contracting sector. Project Management Journal35(1), 24–29.
22.
CaleE. G.JR, & CurleyK. F. (1987). Measuring implementation outcome: Beyond success and failure. Information & Management3(1), 245–253.
23.
CarminesE. G., & McIverS. P. (1981). Analyzing models with unobserved variables: Analysis of covariance structures. In BohrnstedtG. W., & BorgattaE. F. (Eds.), Social Measurement: Current Issues.Beverly Hills, CA: Sage Publications.
24.
CarrilloP., RobinsonH., Al-GhassaniA., & AnumbaC. (2004). Knowledge management in UK construction: Strategies, resources and barriers. Project Management Journal35(1), 46–56.
25.
ChauP. (1997). Reexamining a model for evaluating information center success using a structural equation modeling approach. Decision Sciences28(2), 309–334.
26.
ChenC., FordC. M., & FarrisG. F. (1999). Do rewards benefit the organization? The effects of reward types and the perceptions of diverse R&D professionals. IEEE Transactions on Engineering Management46(1), 47–55.
27.
ChinW. W., & ToddP. A. (1995). On the use, usefulness, and ease of use of structural equation modeling in MIS research: A note of caution. MIS Quarterly19(2), 237–246.
28.
ChurchillG. A. (1979). A paradigm for developing better measures of marketing constructs. Journal of Marketing Research16, 64–73.
29.
CringelyR. X. (1994). When disaster strikes IS: How to forfeit millions in exchange for nothing. Forbes (ASAP Supplement)154(5), 60–64.
30.
CuleP., SchmidtR., LyytinenR., & KeilM. (2000). Strategies for heading off IS project failure. Information Systems Management17(2), 65–73.
31.
DavisF. D., BagozziR. P., & WarshawP. R. (1992). Extrinsic and intrinsic motivation to use computers in the workplace. Journal of Applied Social Psychology22, 1111–1132.
32.
DeciE. (1972). The effects of contingent and non-contingent rewards and controls on intrinsic motivation. Organizational Behavior and Human Performance8, 217–229.
33.
DeCotiisT. A., & DyerL. (1979). Defining and measuring project performance. Research Management22(1), 17–22.
DillonW. R., & GoldsteinM. (1984). Multivariate Analysis Methods and Applications.New York: John Wiley & Sons.
36.
DowningC. E. (1999). System usage behavior as a proxy for user satisfaction: An empirical investigation. Information & Management, 35(4), 203–216.
37.
DunnS. C. (2001). Motivation by project and functional managers in matrix organizations. Engineering Management Journal13(2), 3–9.
38.
EisenhardtK. M. (1988). Agency- and institutional-theory explanations: The case of retail sales compensation. Academy of Management Journal31(3), 488–511.
39.
EisenhardtK. M. (1989a). Building theories from case study research. Academy of Management Review14(4), 532–550.
40.
EisenhardtK. M. (1989b). Agency theory: An assessment and review. Academy of Management Review14(1), 57–74.
41.
Ewusi-MensahK. (1997). Critical issues in abandoned information systems development projects. Communications of the ACM40(9), 74–80.
42.
FarajS., & GeterR. (1998). IS explanations for software development failures.Americas Conference on Information Systems, Baltimore, MD.
43.
FarajS., & SambamurthyV. (2006). Leadership of information systems development projects. IEEE Transactions on Engineering Management53(2), 238–249.
44.
FieldT. (1997). When bad things happen to good projects. CIO11(2), 54–62.
45.
FordR. C., & McLaughlinF. S. (1992). Successful project teams: A study of MIS managers. IEEE Transactions on Engineering Management39(4), 312–317.
46.
FormanM. (2003). Project-level progress. Information Week Summer, 34.
47.
FowlerA., & WalshM. (1999). Conflicting perceptions of success in an information systems project. International Journal of Project Management17(1), 1–10.
48.
FowlerF. J.Jr. (1993). Survey Research Methods.Newbury Park, CA: Sage Publications.
49.
GefenD., StraubD. W., & BoudreauM. C. (2000). Structural equation modeling and regression: Guidelines for research practice. Communications of the AIS4(7), 1–77.
50.
GeldermanM. (1998). The relationship between user satisfaction, usage of information systems and performance. Information & Management34, 11–18.
51.
GlassR. L. (1998). Software Runaways: Lessons Learned from Massive Software Project Failure.Upper Saddle River, NJ: Prentice Hall PTR.
52.
GlassR. L. (1999). Evolving a new theory of project success. Communications of the ACM42(11), 17–19.
53.
HartmanF., & AshrafiR. A. (2002). Project management in the information systems and information technologies industries. Project Management Journal33(3), 5–15.
54.
HatcherL. (1994). A Step-by-Step Approach to Using the SAS System for Factor Analysis and Structural Equation Modeling.Cary, NC: SAS Institute.
55.
HerzbergF. (1966). Work and the Nature of Man.Cleveland, OH: World Publishing Company.
56.
HerzbergF. (1987a). One more time: How do you motivate employees?Harvard Business Review65(5), 109–120.
57.
HerzbergF. (1987b). Workers’ needs: The same around the world. Industry Week234(6), 29–32.
58.
HildebrandC. (1998). If at first you don't succeed. CIO Enterprise Section2(April 15), 31–40.
59.
HwangY. (2005). Investigating enterprise systems adoption: Uncertainty avoidance, intrinsic motivation, and the technology acceptance model. European Journal of Information Systems14(2), 150–161.
60.
JergeasG. F., CookeV. G., & HartmanF. T. (1999). Value engineering incentive clauses. Cost Engineering41(3), 25–34.
61.
JiangJ. J., KleinG., HwangH. G., HuangJ., & HungS. Y. (2004). An exploration of the relationship between software development process maturity and project performance. Information & Management41(3), 279–288.
62.
JohnsonD. E. (1998). Applied Multivariate Methods for Data Analysis.Pacific Grove, CA: Brooks/Cole Publishing.
63.
JohnsonJ. (1995). Chaos: The dollar drain of IT project failures. Application Development Trends2(1), 41–47.
64.
JoreskogK. G. (1993). Testing structural equation models. In BollenK., & LongJ. S. (Eds.)., Testing Structural Equation Models (pp. 294–316). Newbury Park, CA: Sage Publications.
65.
KowthaN. R. (1997). Skills, incentives, and control: An integration of agency and transaction cost approaches. Group & Organization Management22(1), 53–86.
66.
LedererA. L., & PrasadJ. (1992). Nine management guidelines for better cost estimating. Communications of the ACM35(2), 51–59.
67.
LiE. Y. (1997). Perceived importance of information system success factors: A meta analysis of group differences. Information & Management32, 15–28.
68.
LoveP. E. D., IraniZ., & EdwardsD. J. (2003). Learning to reduce rework in projects: Analysis of firm's organizational learning and quality practices. Project Management Journal34(3), 13–25.
69.
LucasH. (1975). Why Information Systems Fail.New York: Columbia University Press.
70.
MartinezE. V. (1994). Avoiding large-scale information systems project failure: The importance of fundamentals. Project Management Journal25(2), 17–25.
71.
McLeanE. R., SmitsS. J., & TannerJ. R. (1996). The importance of salary on job and career attitudes of information systems professionals. Information & Management30(6), 291–299.
72.
McManusJ., & Wood-HarperT. (2003). Information systems project management: The price of failure. Management Services47(5), 16–19.
73.
MendozaL. E., PerezM., & GrimánA. (2006). Critical success factors for managing systems integration. Information Systems Management23(2), 56–75.
74.
MerwinR. E. (1978). Software management: We must find a way. IEEE Transactions on Software Engineering4(4), 307–308.
75.
MillerJ. S., WisemanR. M., & Gomez-MejiaL. R. (2002). The fit between CEO Compensation design and firm risk. Academy of Management Journal45(4), 745–756.
76.
MitchellV., & ZmudR. W. (1999). The effects of coupling IT and work process strategies in redesign projects. Organization Science10(4), 424–438.
77.
MoynihanT. (2002). Coping with client-based 'people-problems': The theories-of-action of experienced IS/software project managers. Information & Management39(5), 377–390.
78.
NelsonB. (1994). 1001 Ways to Reward Employees.New York: Workman Publishing.
NidumoluS. R., & SubramaniM. R. (2004). The matrix of control: Combining process and structure approaches to managing software development. Journal of Management Information Systems20(3), 159–196.
81.
O'DriscollM. P., & RandallD. M. (1999). Perceived organisational support, satisfaction with rewards, and employee job involvement and organisational commitment. Applied Psychology48(2), 197–209.
82.
PintoJ. K., & SlevinD. P. (1988). Project success: Definitions and measurement techniques. Project Management Journal19(1), 67–72.
83.
PintoJ. K., & MantelS. J.Jr. (1990). The causes of project failure. IEEE Transactions on Engineering Management37(4), 269–276.
84.
PodsakoffP. M., & OrganD. W. (1986). Self-reports in organizational research: Problems and prospects. Journal of Management12(4), 531–544.
85.
PrabhakarG. P. (2005). An empirical study reflecting the importance of transformational leadership on project success across twenty-eight nations. Project Management Journal36(4), 53–60.
86.
RaghuT. S., SenP. K., & RaoH. R. (2003). Relative performance of incentive mechanisms: Computational modeling and simulation of delegated investment decisions. Management Science49(2), 160–178.
87.
RaschR. H., & TosiH. L. (1992). Factors affecting software developers’ performance: An integrated approach. MIS Quarterly16(3), 395–409.
88.
RossJ. K. (2004). Project and requirements management - Driving software project success. Journal of Validation Technology10(3), 192–209.
89.
RoyV., BernierC., & LeveilleL. (2006). The high wire balancing act of the IS project director. Database for Advances in Information Systems37(1), 8–39.
90.
RoyerI. (2003). Why bad projects are so hard to kill. Harvard Business Review81(2), 48–56.
91.
SanchezA. M., & PerezM. P. (2004). Early warning signals for R&D projects: An empirical study. Project Management Journal35(1), 11–23.
92.
SegarsA. H., & GroverV. (1993). Re-examining ease of use and usefulness: A confirmatory factor analysis. MIS Quarterly17(4), 517–525.
93.
ShenharA. J. (1998). From theory to practice: Toward a typology of project-management styles. IEEE Transactions on Engineering Management45(1), 33–48.
94.
SlevinD. P., & PintoJ. K. (1986). The project implementation profile: New tool for project managers. Project Management Journal17(4), 57–70.
95.
SmithA. D. (2003). Surveying practicing project managers on curricular aspects of project management programs: A resource-based approach. Project Management Journal34(2), 26–33.
96.
SmithA. D., & FlanegiF. R. (2006). Financial success and time-management factors in a chemical environment: A case study. Project Management Journal37(1), 41–51.
97.
SmithH. J., KeilM., & DepledgeG. (2001). Keeping mum as the project goes under: Toward an explanatory model. Journal of Management Information Systems18(2), 189–227.
98.
StawB. M., CalderB. J., HessR. K., & SandelandsL. E. (1980). Intrinsic motivation and norms about payment. Journal of Personality48, 1–14.
99.
SuardiL. (2004). How to manage your software product life cycle with MAUI. Communications of the ACM47(3), 89–94.
100.
TosiH. L., KatzJ. P., & Gomez-MejiaL. R. (1997). Disaggregating the agency contract: The effects of monitoring, incentive alignment, and term in office on agent decision making. Academy of Management Journal40(3), 584–602.
101.
WangE. T., ShihG. S. P., JiangJ. J., & KleinG. (2006). The relative influence of management control and user-IS personnel interaction on project performance. Information and Software Technology48(3), 214–220.
102.
WardJ. A. (1994). Productivity through project management: Controlling the project variables. Information Systems Management11(1), 16–21.
103.
WiersmaU. J. (1991). Combined effects of intrinsic and extrinsic rewards on motivation. Psychological Reports68(3), 871–882.
104.
ZhangH., & FlynnP. (2003). Effectiveness of alliances between operating companies and engineering companies. Project Management Journal34(3), 48–52.
