S/W개발자의 IT 프로젝트 참여 의도 연구: 조절초점에 따른 프로젝트 기술 최신성의 효과를 중심으로 = S/W Developer`s IT Project Participation: Focusing on the Moderating Role of Regulatory Focus on the Effect of Technology Recency on Participation Intention

다국어 초록 (Multilingual Abstract)

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.

참고문헌 (Reference)

1 Aaker, J. L., "“I” seek pleasures and “we” avoid pains: The role of self-regulator y goals in information processing and persuasion" 28 (28): 33-49, 2001

2 Oz, E., "Why information systems projects are abandoned:a leadership and communication theory and exploratory study" 41 (41): 66-78, 2000

3 Procaccino, J. D., "What do software practitioners really think about project success: an exploratory study" 78 (78): 194-203, 2005

4 Levitt, S. D., "Viewpoint:On the generalizability of lab behaviour to the field" 40 (40): 347-370, 2007

5 Venkatesh, V., "User acceptance of information technology: Toward a unified view" 27 (27): 425-478, 2003

6 Boehm, B. W., "Understanding and controlling software costs" 8 (8): 32-68, 1988

7 Da Silva, F. Q. B., "Towards understanding the underlying structure of motivational factors for software engineers to guide the definition of motivational programs" 85 (85): 216-226, 2012

8 Ajzen, I., "The theory of planned behavior" 50 (50): 179-211, 1991

9 Lee, A. Y., "The pleasures and pains of distinct self-construals: the role of interdependence in regulatory focus" 78 (78): 1122-, 2000

10 Smith, D. C., "The personality of the systems analyst: an investigation" 12 (12): 12-14, 1989

11 Nandhakumar, J., "The fiction of methodological development:a field study of information systems development" 12 (12): 176-191, 1999

12 Kautz, K., "The enactment of methodology: the case of developing a multimedia information system" 55-, 2004

13 Cohen, S. G., "The effectiveness of self-managing teams: A quasi-experiment" 47 (47): 13-43, 1994

14 Guinan, P. J., "The effective use of automated application development tools" 36 (36): 124-139, 1997

15 Bradley, J. H., "The effect of personality type on team performance" 16 (16): 337-353, 1997

16 Sassenberg, K., "The attraction of social power:The inf luence of constr uing power as opportunity versus responsibility" 48 (48): 550-555, 2012

17 Butler, T., "The Relationship between User Participation and the Management of Change Surrounding the Development of Information Systems: A European Perspective’" 13 (13): 12-25, 2001

18 Boehm, B. W., "Software engineering economics" Prentice-hall 1981

19 Linberg, K. R., "Software developer perceptions about software project failure:a case study" 49 (49): 177-192, 1999

20 Judd, C. M., "Research methods in social relations" 1991

21 Crowe, E., "Regulatory focus and strategic inclinations:Promotion and prevention in decisionmaking" 69 (69): 117-132, 1997

22 Shah, J., "Regulatory concerns and appraisal efficiency :the general impact of promotion and prevention" 80 (80): 693-, 2001

23 Higgins, E. T., "Promotion and prevention:Regulatory focus as amotivational principle" 30 : 1-46, 1998

24 Liberman, N., "Promotion and prevention choices between stability and change" 77 (77): 1135-, 1999

25 McConnell, S., "Problem programmers" 15 (15): 126-128, 1998

26 Brendl, C. M., "Principles of judging valence: What makes events positive or negative?" 28 : 95-160, 1996

27 Capretz, L. F., "Personality t ypes i n software engineering" 58 (58): 207-214, 2003

28 Davis, F. D., "Perceived usefulness, perceived ease of use, and user acceptance of information technology" 13 (13): 319-340, 1989

29 Spector, P. E., "Perceived control by employees: A meta-analysis of studies concerning autonomy and participation at work" 39 (39): 1005-1016, 1986

30 Orne, M. T., "On the social psychology of the psychological experiment :With particular reference to demand characteristics and their implications" 17 (17): 776-, 1962

31 Beecham, S., "Motivation in Software Engineering: A systematic literature review" 50 (50): 860-878, 2008

32 Couger, J. D., "Motivating and managing computer personnel" Wiley 1980

33 Camacho, C. J., "Moral value transfer from regulatory fit: what feels right is right and what feels wrong is wrong" 84 (84): 498-, 2003

34 Sharp, H., "Models of motivation in software engineering" 51 (51): 219-233, 2009

35 Scott, J. E., "Managing risks in enterprise systems implementations" 45 (45): 74-81, 2002

36 Higgins, E. T., "Making a good decision: value from fit" 55 (55): 1217-, 2000

37 Myers, I. B., "MBTI manual:A guide to the development and use of the Myers-Briggs Type Indicator" Consulting Psychologists Press 1998

38 Feldt, R., "Links between the personalities, views and attitudes of software engineers" 52 (52): 611-624, 2010

39 Falk, A., "Lab experiments are a major source of knowledge in the social sciences" 326 (326): 535-538, 2009

40 Janz, B. D., "Knowledge worker team effectiveness:The role of autonomy, interdependence, team development, and contextual support variables" 50 (50): 877-904, 1997

41 Hohmann, L., "Journey of the software professional: a sociology of software development" Prentice-Hall 1996

42 Schwalbe, K., "Information technology project management" Cengage Learning 2015

43 Lyytinen, K., "Information systems failures: a survey and classification of the empirical literature" 4 (4): 257-309, 1987

44 Jones, M. C., "IS project team performance : an empirical assessment" 31 (31): 57-65, 1996

45 Cruz, S., "Forty years of research on personality in software engineering: A mapping study" 46 : 94-113, 2015

46 McLeod, L., "Factors that affect software systems development project outcomes: A survey of research" 43 (43): 24-, 2011

47 Rasch, R. H., "Factors affecting software developers’ performance:an integrated approach" 16 (16): 395-413, 1992

48 Bardsley, N., "Experimental economics and the artificiality of alteration" 12 (12): 239-251, 2005

49 Shah, J., "Expectancy× value effects: Regulatory focus as determinant of magnitude and direction" 73 (73): 447-, 1997

50 Kitchenham, B. A., "Evidence-based software engineering" IEEE Computer Society 273-281, 2004

51 Higgins, E. T., "Emotional responses to goal attainment: strength of regulatory focus as moderator" 72 (72): 515-, 1997

52 Venkatesh, V., "Determinants of perceived ease of use: Integrating control, intrinsic motivation, and emotion into the technology acceptance model" 11 (11): 342-365, 2000

53 Calder, B. J., "Designing research for application" 8 (8): 197-207, 1981

54 Roese, N. J., "Counterfactual thinking and regulatory focus: Implications for action versus inaction and suff iciency versus necessity" 77 (77): 1109-, 1999

55 Faraj, S., "Coordinating expertise in software development teams" 46 (46): 1554-1568, 2000

56 Constantine, L. L., "Constantine on peopleware" Prentice Hall 1995

57 Turley, R. T., "Competencies of exceptional and nonexceptional software engineers" 28 (28): 19-38, 1995

58 Fitzgerald, B., "Categories and Contexts of Information Systems Development: Making Sense of the Mess" ECIS 194-211, 1999

59 Procaccino, J. D., "Case study:factors for early prediction of software development success" 44 (44): 53-62, 2002

60 Higgins, E. T., "Beyond pleasure and pain" 52 (52): 1280-, 1997

61 Lenberg, P., "Behavioral software engineering: A definition and systematic literature review" 107 : 15-37, 2015

62 Taylor, S., "Assessing IT usage: The role of prior experience" 19 (19): 561-570, 1995

63 Koufaris, M., "Applying the technology acceptance model and flow theory to online consumer behavior" 13 (13): 205-223, 2002

64 Fitzgerald, B., "An empirica llygrounded framework for the information systems development process" Association for Information Systems 103-114, 1998

65 Haws, K. L., "An assessment of chronic regulatory focus measures" 47 (47): 967-982, 2010

66 Kirton, M. J., "Adapters and Innovators:Styles of Creativity and Problem Solving" Routledge 1994

67 Venkatesh, V., "A theoretical extension of the technology acceptance model: Four longitudinal field studies" 46 (46): 186-204, 2000

68 Hall, T., "A systematic review of theory use in studies investigating the motivations of software engineers" 18 (18): 10-, 2009

69 Hannay, J. E., "A systematic review of theory use in software engineering experiments" 33 (33): 87-107, 2007

70 Kim, J.-H., "A scenariobased experiment and a f ield study: A comparative examination for service failure and recovery" 41 : 125-132, 2014

71 Curtis, B., "A field study of the software design process for large systems" 31 (31): 1268-1287, 1988

72 Poulymenakou, A., "A contingency framework for the investigation of information systems failure" 5 (5): 34-46, 1996