|
Stop IT Project Failures
This book is about information systems development failures and how to avoid them.
It considers what goes wrong with information systems development projects and what actions may be taken to avoid potential difficulties.The reduction of the impact,or even the elimination of the problems,is discussed in terms of an information systems risk
management programme.
Stop I.T.Project failure helps to ensure that IS project managers are successful in helping to deliver application systems. However, IS development risk can never be entirely eliminated and consequently the practitioner needs to bear in mind that an IS development project is never without risk, and hence there is a continuing potential for something to go wrong.
The book covers the key issues and variables and makes specific practical suggestions about the good management practice that is required to implement IS project risk processes.
Dr. Dan Remenyi has spent more than 25 years working in the field of corporate computers and information systems. He has worked with computers as an IS professional, business consultant and user. In all these capacities he has been primarily concerned with benefit realisation and obtaining the maximum value for money from the organisations' information systems investment and effort. He has worked extensively in the field of information systems project management, specialising in the area of project risk identification and management. He has written a number of books and papers in the field of IT management and regularly conducts courses and seminars as well as working as a consultant in this area. Dr.Dan Remenyi holds a B.Soc.Sc., an MBA and a PhD. He is a Visiting Professor at Chalmers University of Technology in Gothenberg, Sweden and an associate member of faculty at Henley Management College in the United Kingdom.
asks what goes wrong with IT projects
shows how to perform a financial analysis for the risks looks at how to minimise the impact
shows you how to manage a risk program
PUBLISHER COMMENTS:
It considers what goes wrong with information systems development projects and what actions may be taken to avoid potential difficulties.The reduction of the impact,or even the elimination of the problems,is discussed in terms of an information systems risk management programme.Stop I.T.Project failure helps to ensure that IS project managers are successful in helping to deliver application systems. However, IS development risk can never be entirely eliminated and consequently the practitioner needs to bear in mind that an IS development project is never without risk, and hence there is a continuing potential for something to go wrong.The book covers the key issues and variables and makes specific practical suggestions about the good management practice that is required to implement IS project risk processes. Dr. Dan Remenyi has spent more than 25 years working in the field of corporate computers and information systems. He has worked with computers as an IS professional, business consultant and user. In all these capacities he has been primarily concerned with benefit realisation and obtaining the maximum value for money from the organisations' information systems investment and effort. He has worked extensively in the field of information systems project management, specialising in the area of project risk identification and management. He has written a number of books and papers in the field of IT management and regularly conducts courses and seminars as well as working as a consultant in this area. Dr.Dan Remenyi holds a B.Soc.Sc., an MBA and a PhD. He is a Visiting Professor at Chalmers University of Technology in Gothenberg, Sweden and an associate member of faculty at Henley Management College in the United Kingdom.
Preface; Information systems project risk management; What goes wrong with IS development projects; Risk, control and time; The major risks; The major consequences; Financial analysis of risk; The major risk drivers; Relationships and ripple effects; Minimising the impact; Managing risk programmes; A case study; Starting an IS risk management programme; Appendices; Index.
|
