S/W Developer's IT Project Participation: Focusing on the Moderating Role of Regulatory Focus on the Effect of Technology Recency on Participation Intention

S/W개발자의 IT 프로젝트 참여 의도 연구: 조절초점에 따른 프로젝트 기술 최신성의 효과를 중심으로

  • Published : 2017.06.01


In the success of an IT project, the role of S/W developer in carrying out the project is critical and crucial. However, compared to its importance, there is only a few studies on the role of human resources in software engineering field, mainly focusing on technology. Based on regulatory focus theory, this study examines how the effect of technology recency on developer's intention to participate in the IT project changes depending on the regulatory focus of the software developer. As a result of the experiment, it was confirmed that there is a difference in the effect of technology recency on project participation intention according to the condition of developer's regulatory focus. This study is meaningful because it extends regulatory focus theory to software engineering field and made theoretical contribution to the research field of behavioral software engineering. In practical, it was possible to suggest a way to improve the intention of the developer to participate in the project, by understanding the software developer in the IT project, considering the software developer propensity and project characteristics.


  1. Aaker, J. L. and Lee, A. Y. 2001, ""I" seek pleasures and "we" avoid pains: The role of self-regulator y goals in information processing and persuasion", Journal of Consumer Research (28:1), pp. 33-49.
  2. Ajzen, I. 1991, "The theory of planned behavior", Organizational Behavior and Human Decision Processes (50:2), pp. 179-211.
  3. Bardsley, N. 2005, "Experimental economics and the artificiality of alteration", Journal of Economic Methodology (12:2), pp. 239-51.
  4. Beecham, S., Baddoo, N., Hall, T., Robinson, H. and Sharp, H. 2008, "Motivation in Software Engineering: A systematic literature review", Information and Software Technology (50:9), pp. 860-78.
  5. Boehm, B. W. 1981, Software engineering economics, Prentice-hall Englewood Cliffs (NJ).
  6. Boehm, B. W. 1988, " Understanding and controlling software costs", Journal of Parametrics (8:1), pp. 32-68.
  7. Bradley, J. H. and Hebert, F. J. 1997, "The effect of personality type on team performance", Journal of Management Development (16:5), pp. 337-53.
  8. Brendl, C. M. and Higgins, E. T. 1996, "Principles of judging valence: What makes events positive or negative?", Advances in experimental social psychology (28), pp. 95-160.
  9. Butler, T. and Fitzgerald, B. 2001, "The Relationship between User Participation and the Management of Change Surrounding the Development of Information Systems: A European Perspective'", Journal of End User Computing (13:1), pp. 12-25.
  10. Calder, B. J., Phillips, L. W. and Tybout, A. M. 1981, "Designing research for application", Journal of Consumer Research (8:2), pp. 197-207.
  11. Camacho, C. J., Higgins, E. T. and Luger, L. 2003, "Moral value transfer from regulatory fit: what feels right is right and what feels wrong is wrong", Journal of Personality and Social Psychology (84:3), pp. 498.
  12. Capretz, L. F. 2003, "Personality types in software engineering", International Journal of Human-Computer Studies (58:2), pp. 207-14.
  13. Cohen, S. G. and Ledford, G. E. 1994, "The effectiveness of self-managing teams: A quasi-experiment", Human relations(47:1), pp. 13-43.
  14. Constantine, L. L. 1995, Constantine on peopleware, Prentice Hall.
  15. Couger, J. D. and Zawacki, R. A. 1980, Motivating and managing computer personnel, Wiley. 16 .
  16. Crowe, E. and Higgins, E. T. 1997, "Regulatory focus and strategic inclinations: Promotion and prevention in decisionmaking", Organizational Behavior and Human Decision Processes (69:2), pp. 117-32.
  17. Cruz, S., da Silva, F. Q. B. and Capretz, L. F. 2015, "Forty years of research on personality in software engineering: A mapping study", Computers in Human Behavior (46), pp. 94-113.
  18. Curtis, B., Krasner, H. and Iscoe, N. 1988, "A field study of the software design process for large systems", Communications of the ACM (31:11), pp. 1268-87.
  19. Da Silva, F. Q. B. and Franca, A. C. C. 2012, "Towards understanding the underlying structure of motivational factors for software engineers to guide the definition of motivational programs", Journal of Systems and Software (85:2), pp. 216-26.
  20. Davis, F. D. 1989, "Perceived usefulness, perceived ease of use, and user acceptance of information technology", MIS Quarterly (13:3), pp. 319-40.
  21. Falk, A. and Heckman, J. J. 2009, "Lab experiments are a major source of knowledge in the social sciences", Science (326:5952), pp. 535-38.
  22. Faraj, S. and Sproull, L. 2000, "Coordinating expertise in software development teams", Management Science (46:12), pp. 1554-68.
  23. Feldt, R., Angelis, L., Torkar, R. and Samuelsson, M. 2010, "Links between the personalities, views and attitudes of software engineers", Information and Software Technology (52:6), pp. 611-24.
  24. Fitzgerald, B. 1998 , "An empirically-grounded framework for the information systems development process", in Proceedings of the international conference on Information systems , Association for Information Systems, pp. 103-14.
  25. Fitzgerald, B. and Fitzgerald, G. 1999, "Categories and Contexts of Information Systems Development: Making Sense of the Mess", in ECIS, Citeseer, pp. 194-211.
  26. Guinan, P. J., Cooprider, J. G. and Sawyer, S. 1997, "The effective use of automated application development tools", IBM Systems Journal (36:1), pp. 124-39.
  27. Hall, T., Baddoo, N., Beecham, S., Robinson, H. and Sharp, H. 2009, "A systematic review of theory use in studies investigating the motivations of software engineers", ACM Transactions on Software Engineering and Methodology (TOSEM) (18:3), pp. 10.
  28. Hannay, J. E., Sjoberg, D. I. K. and Dyba, T. 2007, "A systematic review of theory use in software engineering experiments", IEEE Transactions on Software Engineering (33:2), pp. 87-107.
  29. Haws, K. L., Dholakia, U. M. and Bearden, W. O. 2010, "An assessment of chronic regulatory focus measures", Journal of Marketing Research (47:5), pp. 967-82.
  30. Higgins, E. T. 1997, "Beyond pleasure and pain", American Psychologist (52:12), pp. 1280.
  31. Higgins, E. T. 1998 , "Promotion and prevention : Regulatory focus as a motivation alprinciple ", Advances in experimental social psychology (30), pp. 1-46.
  32. Higgins, E. T. 2000, "Making a good decision: value from fit", American Psychologist (55:11), pp. 1217.
  33. Higgins, E. T., Shah, J. and Friedman, R. 1997, "Emotional responses to goal attainment: strength of regulatory focus as moderator", Journal of Personality and Social Psychology (72:3), pp. 515.
  34. Hohmann, L. 1996, Journey of the software professional: a sociology of software development, Prentice-Hall.
  35. Janz, B . D., Colquitt, J. A. and Noe, R. A. 1997, "Knowledge worker team effectiveness: The role of autonomy, interdependence, team development, and contextual support variables", Personnel Psychology (50:4), pp. 877-904.
  36. Jones, M. C. and Harrison, A. W. 1996, "IS project teamper formance : an empirical assessment", Information & Management (31:2), pp. 57-65.
  37. Judd, C. M., Smith, E. R. and Kidder, L. H. 1991, Research methods in social relations, Holt, Rinehart, and Winston.
  38. Kautz, K. 2004, "The enactment of methodology: the case of developing a multimedia information system", ICIS 2004 Proceedings, pp. 55.
  39. Kim, J.-H. and Jang, S. S. 2014, "A scenariobased experiment and a field study: A comparative examination for service failure and recovery", International Journal of Hospitality Management (41), pp. 125-32.
  40. Kirton, M. J. 1994, "Adapters and Innovators: Styles of Creativity and Problem Solving", in, Routledge, New York.
  41. Kitchenham, B. A., Dyba, T. and Jorgensen, M. 2004, "Evidence-baseds of tware engineering", in Proceedings of the 26th international conference on software engineering, IEEE Computer Society, pp. 273-81.
  42. Koufaris, M. 2002, "Applying the technology acceptance model and flow theory to online consumer behavior", Information Systems Research (13:2), pp. 205-23.
  43. Lee, A. Y., Aaker, J. L. and Gardner, W. L. 2000, "The pleasures and pains of distinct self-construals: the role of interdependence in regulatory focus", Journal of Personality and Social Psychology (78:6), pp. 1122.
  44. Lenberg, P., Feldt, R. and Wallgren, L. G. 2015, "Behavioral software engineering: A definition and systematic literature review", Journal of Systems and Software (107), pp. 15-37.
  45. Levitt, S. D. and List, J. A. 2007, "Viewpoint: On the generalizability of lab behaviour to the field", Canadian Journal of Economics/Revue canadienne d'économique (40:2), pp. 347-70.
  46. Liberman, N., I dson, L. C., Camacho, C. J. and Higgins, E. T. 1999, "Promotion and prevention choices between stability and change", Journal of Personality and Social Psychology (77:6), pp. 1135.
  47. Linberg, K. R. 1999, "Software developer perceptions about software project failure: a case study", Journal of Systems and Software (49:2), pp. 177-92.
  48. Lyytinen, K. and Hirschheim, R. 1987, "Information systems failures: a survey and classification of the empirical literature", Oxford Surveys in Information Technology (4:1), pp. 257-309.
  49. McConnell, S. 1998, "Problem programmers", IEEE Software(15:2), pp. 126-28.
  50. McLeod, L. and MacDonell, S. G. 2011, "Factorst hat affect software systems development project outcomes: A survey of research", ACM Computing Surveys (CSUR) (43:4), pp. 24.
  51. Myers, I. B., McCaulley, M . H., Quenk, N. L. and Hammer, A. L. 1998, MBTI manual: A guide to the development and use of the Myers-Briggs Type Indicator, Consulting Psychologists Press Palo Alto, CA.
  52. Nandhakumar, J. and Avison, D. E. 1999, "The fiction of methodological development: a field study of informations ystems development", Information Technology & People(12:2), pp. 176-91.
  53. Orne, M. T. 1962, "On the social psychology of the psychological experiment : With particular reference to demand characteristics and their implications", American Psychologist (17:11), pp. 776.
  54. Oz, E. and Sosik, J. J. 2000, "Why information systems projects are abandoned: a leadership and communication theory and exploratory study", Journal of Computer Information Systems (41:1), pp. 66-78.
  55. Poulymenakou, A. and Holmes, A. 1996, "A contingency framework for the investigation of information systems failure", European Journal of Information Systems(5:1), pp. 34-46.
  56. Procaccino, J. D., Verner, J . M., Overmyer, S. P. and Darter, M. E. 2002, "Case study: factors for early prediction of software development success", Information and Software Technology (44:1), pp. 53-62.
  57. Procaccino, J. D ., Verner, J . M., S helfer, K. M. and Gefen, D. 2005, "What do software practitioners really think about project success: an exploratory study", Journal of Systems and Software (78:2), pp. 194-203.
  58. Rasch, R. H. and Tosi, H. L. 1992, "Factors affecting software developers' performance: an integrated approach", MIS Quarterly (16:3), pp. 395-413.
  59. Roese, N. J., Hur, T. and Pennington, G. L. 1999, "Counterfactual thinking and regulatory focus: Implications for action versus inaction and suff iciency versus necessity", Journal of Personality and Social Psychology (77:6), pp. 1109.
  60. Sassenberg, K., Ellemers, N. and Scheepers, D. 2012, "The attraction of social power: The inf luence of constr uing power as opportunity versus responsibility", Journal of Experimental Social Psychology (48:2), pp. 550-55.
  61. Schwalbe, K. 2015, Information technology project management, 7ed., Cengage Learning.
  62. Scott, J. E. and Vessey, I. 2002, "Managing risks in enterprise systems implementations", Communications of the ACM(45:4), pp. 74-81.
  63. Shah, J. and Higgins, E. T. 1997, "Expectancy x value effects: Regulatory focus as determinant of magnitude and direction", Journal of Personality and Social Psychology (73:3), pp. 447.
  64. Shah, J. and Higgins, E. T. 2001, "Regulatory concerns and appraisal efficiency: the general impact of promotion and prevention", Journal of Personality and Social Psychology (80:5), pp. 693.
  65. Sharp, H., Baddoo, N., Beecham, S., Hall, T. and Robinson, H. 2009, "Models of motivation in software engineering", Information and Software Technology (51:1), pp. 219-33.
  66. Smith, D. C. 1989, " The personality of the systems analyst: an investigation", ACM SIGCPR Computer Personnel (12:2), pp. 12-14.
  67. Spector, P. E. 1986, "Perceived control by employees: A meta-analysis of studies concerning autonomy and participation at work", Human Relations (39:11), pp. 1005-16.
  68. Taylor, S. and Todd, P. 1995, "Assessing IT usage: The role of prior experience", MIS Quarterly (19:4), pp. 561-70.
  69. Turley, R. T. and Bieman, J. M. 1995, "Competencies of exceptional and nonexceptional software engineers", Journal of Systems and Software (28:1), pp. 19-38.
  70. Venkatesh, V. 2000, "Determinants of perceived ease of use: Integrating control, intrinsic motivation, and emotion into the technology acceptance model", Information Systems Research (11:4), pp. 342-65.
  71. Venkatesh, V. and Davis, F. D. 2000, "A theoretical extension of the technology acceptance model: Four longitudinal field studies", Management Science (46:2), pp. 186-204.
  72. Venkatesh, V., Morris, M. G., Davis, G. B. and Davis, F. D. 2003, "User acceptance of information technology: Toward a unified view", MIS Quarterly (27:3), pp. 425-78.