Linking strategy, governance, and performance in software engineering

Applying IT in an appropriate and timely way, in harmony with strategies, goals and needs, is important for business performance success. However, because ensuring that IT will support the achievement of business strategies entails a sequence of key decisions in a variety of related IT areas, knowledge that is relevant for effective decision-making tends to be dispersed among multiple business and IT stakeholders, who represent an organisation's diverse and conflicting interests. Consequently, inappropriately assigning decision rights for critical IT decisions increases the risk of misalignment. We study the context in which decision rights are managed as part of governance in software development for business process support so that organisations can achieve high-level alignment between software systems and business processes during software development. In this paper we establish the key components of a system for governance design that links software development governance arrangements, business strategy and performance. We position business process executives and managers as roles responsible for software development governance. Their responsibilities include defining the software system's strategic aims, providing the leadership to put them into effect, and satisfying themselves that an appropriate governance structure is, and remains in place during software development. We also position business process and software developer stakeholders as roles responsible for implementing software systems that help realise strategic aims. We propose four key software development decisions: functional and non-functional requirements, and system architecture and deliverables.

[1]  Yolande E. Chan,et al.  IS project alignment – a process perspective , 2010, J. Inf. Technol..

[2]  Robert W. Zmud,et al.  Arrangements for Information Technology Governance: A Theory of Multiple Contingencies , 1999, MIS Q..

[3]  F. Marton,et al.  On qualitative differences in learning , 2013 .

[4]  Lerina Aversano,et al.  A Framework for Measuring the Alignment between Business Processes and Software Systems , 2009, FGIT-ASEA.

[5]  G. Boulton‐Lewis Teaching for quality learning at university , 2008 .

[6]  Amrit Tiwana,et al.  Governance-Knowledge Fit in Systems Development Projects , 2009, Inf. Syst. Res..

[7]  Yael Dubinsky,et al.  Effective management of roles and responsibilities: Driving accountability in software development teams , 2010, IBM J. Res. Dev..

[8]  George Westerman,et al.  Governance of Strategic IT Projects: A Nomological Network of the Antecedents of Performance , 2007 .

[9]  Paul L Bannerman,et al.  Software development governance: A meta-management perspective , 2009, 2009 ICSE Workshop on Software Development Governance.

[10]  Jason Bennett Thatcher,et al.  Fix IT-business relationships through better decision rights , 2007, CACM.

[11]  Harminder Singh,et al.  Managing diverse stakeholders in enterprise systems projects: a control portfolio approach , 2011, J. Inf. Technol..

[12]  L. Diamond IT Governance : How Top Performers Manage IT Decision Rights for Superior Results , 2005 .

[13]  P. Weill,et al.  IT Governance , 2017 .

[14]  M. C. Jensen,et al.  Specific and General Knowledge and Organizational Structure , 1995 .

[15]  F. Marton,et al.  ON QUALITATIVE DIFFERENCES IN LEARNING—II OUTCOME AS A FUNCTION OF THE LEARNER'S CONCEPTION OF THE TASK , 1976 .

[16]  Jerry N. Luftman,et al.  Enablers and Inhibitors of Business-IT Alignment , 1999, Commun. Assoc. Inf. Syst..