Framework of Goal-driven Risk Management in Software Development Projects Using the Socio-technical Systems Approach

Abstract

Previous studies have identified the influence of goal agreement on requirement elicitation in software projects, but they have not addressed how it influences risks in projects. The purpose of this study is to examine the influence of goal identification and agreement on software project risks. With socio-technical systems theory as the backdrop, we used a goal-oriented perspective to understand how the social subsystem influences the technical subsystem of a software development project. In an empirical study with 411 responses from software project developers and managers in India and using structural equation modelling, the causal linkages between goal orientation and project risk variables have been examined. The results indicated that the early adoption of goal-driven risk management reduces the social context risks which, in turn, reduces the project management risk. The study also revealed that the product artefact is independent of whether the system was completed within budget and schedule. To design the risk management strategy, project managers should consider the relationship between social context risk and project management risk and the implications of these relationships on project performance.

Keywords

Goal oriented project management project performance risk risk management social risk project management risk

Get full access to this article

View all access options for this article.

References

Addison

, & Vallabh

(2002). Controlling software project risks: an empirical study of methods used by experienced project managers [Conference paper]. The 2002 Annual Research Conference of the South African Institute of Computer Scientists and Information Technologists on Enablement Through Technology (pp. 128–140).

Akter

, D’Ambra

, & Ray

(2011). Trustworthiness in mHealth information services: an assessment of a hierarchical model with mediating and moderating effects using partial least squares (PLS). Journal of the Association for Information Science and Technology, 62(1), 100–116.

Alberts

C. J.

, & Dorofee

A. J.

(2010). Risk management framework (No. CMU/SEI-2010-TR-017). Software Engineering Institute, Carnegie Mellon University.

Allen

, Carpenter

, Hutchins

, & Jones

(2015). Impact of risk management on project cost: An industry comparison. Journal of Information Technology & Economic Development, 6(2), 1–19.

Anderson

J. C.

, & Gerbing

D. C.

(1988). Structural equation modeling in practice: A review and recommended two-step approach. Psychological Bulletin, 103(3), 411–423.

Anderson

J. C.

, & Gerbing

D. W.

(1984). The effects of sampling error on convergence, improper solutions, and goodness-of-fit indices for maximum likelihood confirmatory factor analysis. Psychometrika, 49(2), 155–173.

Atkinson

, Crawford

, & Ward

(2006). Fundamental uncertainties in projects and the scope of project management. International Journal of Project Management, 24(8), 687–698.

Bagozzi

R. P.

, & Yi

(1988). On the evaluation of structural equation models. Journal of the Academy of Marketing Science, 16(1), 74–94.

Barber

, & Warn

(2005). Leadership in project management: from firefighter to firelighter. Management Decision, 43(7/8), 1032–1039.

10.

Barki

, Rivard

, & Talbot

(1993). Toward an assessment of software development risk. Journal of Management Information System, 10(2), 203–225.

11.

Bentler

P. M.

(1990). Comparative fit indices in structural models. Psychological Bulletin, 107(2), 238–246.

12.

Bentler

P. M.

, & Bonett

D. G.

(1980). Significant tests and goodness of fit in the analysis of covariance structure. Psychological Bulletin, 88(3), 588–606.

13.

Bentler

P. M.

, & Chou

C. P.

(1987). Practical issues in structural modeling. Sociological Methods and Research, 16(1), 78–117.

14.

Bhoola

, Hiremath

S. B.

, & Mallik

(2014). An assessment of risk response strategies practiced in software projects. Australasian Journal of Information Systems, 18(3).

15.

Boehm

(1989). Software risk management. In European Software Engineering Conference (pp. 1–19).

16.

Boehm

(1991). Software risk management: Principles and perspective. IEEE, 8(1), 32–41.

17.

Boehm

, Madachy

, & Selby

(1995). Cost models for future software life cycle processes COCOMO 2.0, Annals of Software Engineering, 1(1), 57–94.

18.

Brown

Y. F.

, Canal

, Cullen

, Elliott

, Faulkner

, Lackner

, Owens

, Peercy

, Reisz

, Tempel

, & Trellue

(2000). Software risk management: A practical guide. Department of energy quality managers software quality assurance subcommittee reference document SQAS21.01.00.

19.

Calamel

, Defélix

, Picq

, & Retour

(2012). Inter-organisational projects in French innovation clusters: The construction of collaboration. International Journal of Project Management, 30, 48–59.

20.

Carbone

T. A.

, & Tippett

D. D.

(2004). Project risk management using the project risk FMEA. Engineering Management Journal, 16(4), 28–35.

21.

Chakraborty

, Sarker

, & Sarker

(2010). An exploration into the process of requirements elicitation: A grounded approach. Journal of the association for information systems, 11(4), 212.

22.

Chang

, Yen

, Chiang

, & Parolia

(2013). Knowledge contribution in information system development teams: an empirical research from a social cognitive perspective. International Journal of Project Management, 31, 252–263.

23.

Chiang

I. R.

, & Mookerjee

V. S.

(2004). Improving software team productivity. Communications of the ACM, 47(5), 89–93.

24.

Chiocchio

, Forgues

, Paradis

, & Iordanova

(2011). Teamwork in integrated design projects: Understanding the effects of trust, conflict, and collaboration on performance. Project Management Journal, 42(6), 78–91.

25.

Conboy

, & Morgan

(2011). Beyond the customer: Opening the agile systems development process. Information and Software Technology, 53(5), 535–542.

26.

Cooke-Davies

(2002). The “real” success factors on projects. International Journal of Project Management, 20(3), 185–190.

27.

Dandage

R. V.

, Mantha

S. S.

, Rane

S. B.

, & Bhoola

(2018). Analysis of interactions among barriers in project risk management. Journal of Industrial Engineering International, 14(1), 153–169.

28.

de Carvalho

M. M.

, & Rabechini

Jr. , (2015). Impact of risk management on project performance: The importance of soft skills. International Journal of Production Research, 53(2), 321–340.

29.

Doty

D. H.

, & Glick

W. H.

(1998). Common methods bias: Does common methods variance really bias results?. Organizational Research Methods, 1, 374–406.

30.

, Keil

, Mathiassen

, Shen

, & Tiwana

(2007). Attention-shaping tools, expertise, and perceived control in IT project risk assessment. Decision Support Systems, 43(1), 269–283.

31.

Emery

F. E.

(1959). Characteristics of socio-technical systems: A critical review of theories and facts about the effects of technological change on the internal structure of work organisations; with special reference to the effects of higher mechanisation and automation. Tavistock Institute of Human Relations.

32.

Fiske

S. T.

, & Kinder

D. R.

(1981). Involvement, expertise, and schema use: Evidence from political cognition. In Nancy

& John

(Eds.), Personality, cognition and social interaction (171–190). Erlbaum.

33.

Foo

S. W.

, & Muruganatham

(2000, November). Software risk assessment model (Conference paper, Vol. 2, pp. 536–544). Proceedings of the 2000 IEEE International Conference on Management of Innovation and Technology. ICMIT 2000. Management in the 21st Century (Cat. No. 00EX457). IEEE.

34.

Fornell

, & Larcker

D. F.

(1981). Evaluating structural equation models with unobserved variables and measurement error. Journal of Marketing Research, 18(1), 39–50.

35.

Globerson

, & Zwikael

(2002). The impact of project manager on project management planning process. Project Management Journal, 33(3), 58–64.

36.

Hair

J. F.

, Ringle

C. M.

, & Sarstedt

(2011). PLS-SEM: Indeed a silver bullet. Journal of Marketing Theory and Practice, 19(2), 139–152.

37.

Han

, & Huang

(2007). An empirical analysis of risk components and performance on software projects. The Journal of Systems and Software, 80(1), 42–50.

38.

Hartono

, Sulistyo

S. R.

, Praftiwi

P. P.

, & Hasmoro

(2014). Project risk: Theoretical concepts and stakeholders’ perspectives. International Journal of Project Management, 32(3), 400–411.

39.

Hatcher

(1994). A step-by-step approach to using the SAS system for factor analysis and structural equation modelling. SAS Institute.

40.

, & King

W. R.

(2008). The role of user participation in information systems development: Implications from a meta-analysis. Journal of Management Information Systems, 25(1), 301–331.

41.

Higuera

R. P.

, & Haimes

Y. Y.

(1996). Software risk management (No. CMU/SEI-96-TR-012). Pittsburgh Software Engineering Institute, Carnegie-Mellon University.

42.

Hsu

J. S. C.

, Chu

T. H.

, Lin

T. C.

, & Lo

C. F.

(2014). Supporting virtual team building with a SS: An empirical investigation. Decision Support Systems, 34(4), 359–367.

43.

Idaszak

J. R.

, & Drasgow

(1987). A revision of job diagnostic survey: Elimination of a measurement artefact. Journal of Applied Psychology, 72(1), 69–74.

44.

Islam

, Mouratidis

, & Weippl

E. R.

(2014). An empirical study on the implementation and evaluation of a goal-driven software development risk management model. Information and Software Technology, 56(2), 117–133.

45.

Jiang

, & Klein

(2000). Software development risks to project effectiveness. The Journal of Systems and Software, 52(1), 3–10.

46.

Jiang

J. J.

, Klein

, & Chen

H. G.

(2006). The effects of user partnering and user nonsupport on project performance. Journal of the Association for Information Systems, 7(1), 68–90.

47.

Jiang

J. J.

, Klein

, & Discenza

(2002). Perception differences of software success: Provider and user views of system metrics. Journal of systems and software, 63(1), 17–27.

48.

Jiang

J. J.

, Klein

, & Ellis

T. S.

(2002). A measure of software development risk. Project Management Journal, 33(3), 30–41.

49.

, & Zhang

(2011). Effects of empowerment on performance in open-source software projects. IEEE Transactions on Engineering Management, 58(2), 334–346.

50.

Keil

, Cule

, Lyytinen

, & Schmidt

(1998). A framework for identifying software project risks. Communications of the ACM, 41(11), 76–83.

51.

Keil

, Rai

, & Liu

(2013). How user risk and requirements risk moderate the effects of formal and informal control on the process performance of IT projects. European Journal of Information Systems, 22(6), 650–672.

52.

Keil

, Rai

Mann

J. E. C.

, & Zhang

G. P.

(2003). Why software projects escalate: The importance of project management constructs. IEEE Transactions on Engineering Management, 50(3), 251–261.

53.

Klein

, & Jiang

J. J.

(2001). Seeking consonance in information systems. Journal of Systems and Software, 56(2), 195–202.

54.

Kontio

(2001). Software engineering risk management: A method, improvement framework, and empirical evaluation [Unpublished doctoral dissertation]. Helsinki University of Technology.

55.

Krosnick

J. A.

(1991). Response strategies for coping with the cognitive demands of attitude measures in surveys. Applied Cognitive Psychology, 5(3), 213–236.

56.

Krosnick

J. A.

(1999). Survey research. Annual Review of Psychology, 50, 537–567.

57.

Krosnick

J. A.

, & Alwin

D. F.

(1987). An evaluation of a cognitive theory of response-order effects in survey measurement. Public Opinion Quarterly, 51(2), 201–219.

58.

Kutsch

(2008). The influence of intervening conditions on the over and underestimation of risk. International Journal of Managing Projects in Business, 1(4), 602–610.

59.

Lamsweerde

A. V.

(2000). Requirements engineering in the year 00: A research perspective (Conference paper, pp. 5–19). Invited Keynote Paper, Proceedings of 22nd International Conference on Software Engineering.

60.

Lapouchnian

(2005). Goal oriented requirements engineering: An overview of current research [Symposium, pp. 249–263]. Proceedings RE’01, 5th IEEE International Symposium on Requirements Engineering, Toronto.

61.

Larson

(1997). Partnering on construction projects: A study of the relationship between partnering activities and project success. IEEE Transactions on Engineering Management, 44(2), 188–195.

62.

Laumer

(2011). Why do people reject technologies – a literature-based discussion of the phenomena “resistance to change” [Conference paper]. ECIS 2011 Proceedings of the Information Systems and Managerial Psychology Research.

63.

Lee

, Chou

, & Chen

(2020). The effect of process tailoring on software project performance: The role of team absorptive capacity and its knowledge-based enablers. Information Systems Journal, 31, 120–147.

64.

Lee

, Park

, & Lee

(2015). Raising team social capital with knowledge and communication in information systems development projects. International Journal of Project Management, 33, 797–807.

65.

Letier

(2001). Reasoning about agents in goal-oriented requirements engineering [PhD. thesis]. University of Louvain.

66.

Lim

C. S.

, & Mohamed

M. Z.

(1999). Criteria of project success: An exploratory re-examination. International Journal of Project Management, 17(4), 243–248.

67.

Liu

G. H.

, Wang

E. T.

, & Chua

C. E. H.

(2015). Leveraging social capital to obtain top management support in complex, cross-functional IT projects. Journals of the Association for Information Systems, 16(1), Article 1.

68.

Liu

J. Y.

, & Chiu

G. C.

(2017). Influence of project partnering on stakeholder role ambiguity and project manager risk perception in information systems project. Project Management Journal, 47(6), 94–110.

69.

Liu

J. Y. C.

, Chiang

J. C.

, Yang

M. H.

, & Klein

(2011). Partnering effects on user-developer conflict and role ambiguity in information system projects. Information and Software Technology, 53(7), 722–729.

70.

Locke

E. A.

, & Latham

G. P.

(2002). Building a practically useful theory of goal setting and task motivation: A 35-year odyssey. American psychologist, 57(9), 705–717.

71.

Maguire

, & Redman

(2007). The role of human resource management in information systems development. Management Decision, 45(2), 252–264.

72.

Manalif

(2013). Fuzzy expert-COCOMO risk assessment and effort contingency model in software project management [Electronic thesis and dissertation repository].

73.

Maruping

L. M.

, Zhang

, & Venkatesh

(2009). Role of collective ownership and coding standards in coordinating expertise in software project teams. European Journal of Information Systems, 18(4), 355–371.

74.

McFarlan

(1982). Portfolio approach to information-systems. Journal of Systems Management, 33(1), 12–19.

75.

Mitchell

V. L.

(2006). Knowledge integration and information technology project performance. Mis Quarterly, 30(4), 919–939.

76.

Nakatsu

R. T.

, & Iacovou

(2009). Comparative study of important risk factors involved in offshore and domestic outsourcing of software development projects: A two-panel Delphi study. Information & Management, 46(1), 57–68.

77.

NASSCOM. (2017, June 15). The IT-BPM industry in India 2017: Strategic review. http://www.nasscom.in/knowledge-center/publications/it-bpm-industry-india-2017-strategic-review

78.

Nelson

R. R.

, & Jansen

K. J.

(2007). IT project management: infamous failures, classic mistakes, and best practices. MIS Quarterly Executive, 6(2), 67–78.

79.

Nelson

R. R.

, & Morris

M. G.

(2014). IT project estimation: Contemporary practices and management guidelines. MIS Quarterly Executive, 13(1), 15–30.

80.

Nidumolu

S. R.

(1996). Standardization, requirements uncertainty and software project performance. Information & Management, 31(3), 135–150.

81.

Patnayakuni

, Rai

, & Tiwana

(2007). Systems development process improvement: A knowledge integration perspective. IEEE Transactions on Engineering Management, 54(2), 286–300.

82.

Pava

C. H.

(1983). Designing managerial and professional work for high performance: A sociotechnical approach. Global Business and Organizational Excellence, 2(2), 126–135.

83.

Pollack

, & Adler

(2015). Does project management affect business productivity. Project Management Journal, 45(6), 17–24.

84.

Pollack

, & Matous

(2019). Testing the impact of targeted team building on project team communication using social network analysis. International Journal of Project Management, 37(3), 473–484.

85.

Podsakoff

P. M.

, MacKenzie

S. B.

, & Podsakoff

N. P.

(2003). Common method bias in behavioural research: A critical review of the literature and recommended remedies. Journal of Applied Psychology, 88(5), 879–903.

86.

Podsakoff

P. M.

, MacKenzie

S. B.

, & Podsakoff

N. P.

(2012). Sources of method bias in social science research and recommendations on how to control it. Annual Review of Psychology, 63, 539–569.

87.

Procaccino

J. D.

, Verner

J. M.

, Overmyer

S. P.

, & Darter

M. E.

(2002). Case study: Factors for early prediction of software development success. Information and Software Techology, 44(1), 53–62.

88.

Project Management Institute. (2013). Organizational project management maturity model (OPM3): Knowledge foundation. Author.

89.

Project Management Institute. (2014). The high cost of low performance. PMI pulse of the profession. Author.

90.

Project Management Institute. (2017). Project management body of knowledge (6th ed.). Author.

91.

Purvis

, Henry

R. M.

, Tams

, Grover

, McGregor

J. D.

, & Davis

(2016). The impact or residual risk and resultant problems on information system development project performance. Project Management Journal, 47(4), 51–67.

92.

Qureshi

, & Fang

(2011). Socialization in open source software projects: A growth mixture modeling approach. Organizational Research Methods, 14(1), 208–238.

93.

Sarker

, Ahuja

, Sarker

, & Kirkeby

(2011). The role of communication and trust in global virtual teams: A social network perspective. Journal of Management Information Systems, 28(1), 273–310.

94.

Sarker

, & Sarker

(2009). Exploring agility in distributed information systems development teams: An interpretive study in an offshoring context. Information Systems Research, 20(3), 440–461.

95.

Sato

, & Hirao

(2013). Optimum budget allocation method for projects with critical risks. International Journal of Project Management, 31(1), 126–135.

96.

Sauer

, Gemino

, & Reich

B. H.

(2007). The impact of size and volatility on IT project performance. Communications of the ACM, 50(11), 79–84.

97.

Saunders

F. C.

, Gale

A. W.

, & Sherry

A. H.

(2015). Conceptualising uncertainty in safety-critical projects: A practitioner perspective. International Journal of Project Management, 33(2), 467–478.

98.

Schmidt

, Lyytinen

, Keil

, & Cule

(2001). Identifying software project risks: An international Delphi study. Journal of Management Information Systems, 17(4), 5–36.

99.

Schwarz

, Hippler

, & Noelle-Neumann

(1992). A cognitive model of response-order effects in survey measurement. In Norbert

& Seymour

(Eds.), Context effects in social and psychological research. Springer-Verlag.

100.

Sethi

, & Iqbal

(2008). Stage-gate controls, learning failure, and adverse effect on novel new products. Journal of Marketing, 72(1), 118–134.

101.

Sharma

, Sengupta

, & Gupta

(2011). Exploring risk dimensions in Indian software industry. Project Management Journal, 42(5), 78–91.

102.

The Standish Group. (2016). Standish group chaos report. https://www.standishgroup.com/outline

103.

Teller

, Kock

, & Gemunden

H. G.

(2014). Risk management in project portfolios is more than managing project risks. Project Management Journal, 45(4), 67–80.

104.

Trist

E. L.

(1981). The evolution of socio-technical systems (Vol. 2). Ontario Quality of Working Life Centre.

105.

Turner

, & Zolin

(2012). Forecasting success on large projects: Developing reliable scales to predict multiple perspectives by multiple stakeholders over multiple time frames. Project Management Journal, 43(5), 87–99.

106.

Verner

J. M.

, & Evanco

W. M.

(2005). In-house software development: What project management practices lead to success? IEEE Software, 22(1), 86–93.

107.

Wallace

, Keil

, & Rai

(2004). How software project risk affects project performance: An investigation of the dimensions of risk and an exploratory model. Decision Science, 35(2), 289–321.

108.

Whittaker

(1999). What went wrong? Unsuccessful information technology projects. Information Management & Computer Security, 7(1), 23–30.

109.

Wienclaw

(2014). Information system project management. EBSCO research starters. Great Neck Publishing.

110.

, Olson

D. L.

, & Dolgui

(2015). Decision making in enterprise risk management: A review and introduction to special issue. Omega, 57, 1–4.

111.

Zmud

R. W.

(1980). Management of large software development efforts. MIS Quarterly, 4, 45–55.

112.

Zwikael

, & Sadeh

(2007). Planning effort as an effective risk management tool. Journal of Operations Management, 25(4), 755–767.