Reporting on Software Development Projects to Senior Managers and the Board

It is contended that the scale of some in-house software projects (and the potential impact of project failure on an organization's operating capabilities and reputation) is such that the progress of those projects warrants the concentrated attention of senior managers (and possibly, the Board). The article utilizes a case study to illustrate how the adoption of key proposals outlined in the business information systems and software engineering literatures for the management of these projects may not necessarily be effective. This work augments Walker and Oliver (2005), which examined the options when accounting for software expenditure and recommended expensing for consistent treatment. This article then reviews the 'information needs' of senior managers, and presents a set of six reporting templates to facilitate the effective monitoring of progress of software projects (including post-migration expenditure on system enhancements and maintenance, and efforts to capture planned benefits). In some circumstances, the scale and risks associated with software development projects warrant oversight of these projects by the Board, possibly through the establishment of specialist 'IT governance' subcommittees. Accordingly, a model charter for an IT governance committee is presented in an appendix.

[1]  小島 大徳,et al.  Principles of Corporate Governance , 2007 .

[2]  N. Demise,et al.  OECD Principles of Corporate Governance , 2006 .

[3]  Gary R. Oliver,et al.  Accounting for Expenditure on Software Development for Internal Use , 2005 .

[4]  R. Walker.  Gaps in Guidelines on Audit Committees , 2004 .

[5]  Robert Buttrick,et al.  The project workout -a toolkit for reaping the rewards from all your business projects 2/E. , 2003 .

[6]  N. Carr.  IT doesn't matter , 2003, IEEE Engineering Management Review.

[7]  Tony Murphy,et al.  Achieving Business Value from Technology: A Practical Guide for Today's Executive , 2002 .

[8]  Xiaotong Li,et al.  Evaluate IT Investment Opportunities Using Real Options Theory , 2002, Inf. Resour. Manag. J..

[9]  Søren L. Buhl,et al.  Underestimating Costs in Public Works Projects: Error or Lie? , 2002, 1303.6604.

[10]  Neal Whitten,et al.  The Enterprize Organization: Organizing Software Projects for Accountability and Success , 1999 .

[11]  Stephen A. Devaux,et al.  Total Project Control: A Manager's Guide to Integrated Project Planning, Measuring, and Tracking , 1999 .

[12]  T. Capers Jones,et al.  Estimating software costs , 1998 .

[13]  Guy Fitzgerald,et al.  Evaluating information systems projects: a multidimensional approach , 1998, J. Inf. Technol..

[14]  Joan A. Ballantine,et al.  Financial appraisal and the IS/IT investment decision making process , 1998, J. Inf. Technol..

[15]  R. Dorf,et al.  The Balanced Scorecard: Translating Strategy Into Action , 1997, Proceedings of the IEEE.

[16]  R. Galliers,et al.  Information systems/technology evaluation practices: evidence from UK organizations , 1996, J. Inf. Technol..

[17]  J. Ward,et al.  Evaluation and realisation of IS/IT benefits: an empirical study of current practice , 1996 .

[18]  Edward Kit,et al.  Software testing in the real world - improving the process , 1995 .

[19]  D. Remenyi,et al.  Effective Measurement and Management of It Costs and Benefits: Key Issues , 1995 .

[20]  R. Balachandra,et al.  Are R&D Project Termination Factors Universal? , 1995 .

[21]  Charles H. Kriebel,et al.  Information Technologies and Business Value: An Analytic and Empirical Investigation , 1995, Inf. Syst. Res..

[22]  Peter G. Neumann,et al.  Computer-related risks , 1994 .

[23]  J. Hares,et al.  Measuring the value of information technology , 1994 .

[24]  Philip Yetton,et al.  False prophecies, successful practice and future directions in IT management , 1994, Business Process Re-Engineering.

[25]  Geoff Hogbin,et al.  Investing in Information Technology; Managing the Decision-Making Process , 1994 .

[26]  Leslie P. Willcocks,et al.  How Do Organizations Evaluate and Control Information Systems Investments? Recent UK Survey Evidence , 1993, Human, Organizational, and Social Dimensions of Information Systems Development.

[27]  Frank F. Land,et al.  Evaluating investments in IT , 1992, J. Inf. Technol..

[28]  David P. Youll,et al.  Making Software Development Visible: Effective Project Control , 1990 .

[29]  Donald J. Reifer,et al.  Software acquisition management - managing the acquisition of custom software systems , 1990, Wiley series in industrial software engineering practice.

[30]  Kuldeep Kumar,et al.  Post implementation evaluation of computer-based information systems: current practices , 1990, Commun. ACM.

[31]  Robert N. Charette,et al.  Software Engineering Risk Analysis and Management , 1989 .

[32]  Peter C. Lockemann,et al.  Cost benefit analysis of information systems: a survey of methodologies , 1988, COCS '88.

[33]  R. Balachandra,et al.  How to Decide When to Abandon a Project : R&D Management , 1980 .

[34]  Anne Nagel,et al.  The Balanced Scorecard Translating Strategy Into Action , 2002 .

[35]  Leslie P. Willcocks,et al.  IT Evaluation Revisited: Plus ça Change ..... , 2001 .

[36]  Pei Hsia.  Making Software Development Visible , 1996, IEEE Software.

[37]  Timothy Braithwaite.  The power of IT : maximizing your technology investments , 1996 .

[38]  Gerry C. Jacobs,et al.  Whose responsibility is IT management , 1995 .

[39]  Anneliese Amschler Andrews,et al.  Software engineering - methods and management , 1990, Int. CMG Conference.

[40]  Martyn A. Ould,et al.  Strategies for software engineering - the management of risk and quality , 1990, Wiley series in software engineering practice.

[41]  E. B. Swanson,et al.  Measuring Business Value of Information Technologies , 1988 .

[42]  Jeffrey K. Pinto,et al.  Critical factors in successful project implementation , 1987, IEEE Transactions on Engineering Management.

[43]  M. Buss.  How to rank computer projects. , 1983, Harvard business review.

[44]  F. McFarlan,et al.  The information archipelago--plotting a course. , 1983, Harvard business review.

[45]  W. S. Turner,et al.  Project auditing methodology , 1980 .

[46]  Fred P. Brooks,et al.  The Mythical Man-Month , 1975, Reliable Software.