The authors start with a chapter on the elusive nature of IT benefits, and the difficulties of measuring and managing them. This chapter lays the groundwork for the rest of the book. One nugget of valuable information given here is the recommendation that IT be run based on P&L (profit and loss). Because IT is traditionally operated as a cost center instead of a profit center I first thought that this was overly radical. However, as I dug deeper I understood the true intent: to tie together investment, value and economics, and measure IT investments based on their derived value to the business. This is where profit comes in. It initially looked like thinly disguised cost/benefit, but the expansion of this concept as the book unfolds makes it look like a true P&L approach.
Chapter two focuses on reasons to evaluate IT investments, and gives a number of approaches to perform evaluations. It covers the strengths and weaknesses of each approach and also discusses some of the pitfalls of benefit evaluation. This material segues into chapter three, which covers the investment decision process. The authors did a good job of explaining this from an IT perspective, and ties it closely to meeting business requirements.
The next chapter discusses the issues associated with, and the techniques used, to perform the IT evaluation. This is where the book gets interesting and a coherent method for measuring IT costs takes shape. What I liked most about this chapter is the list of possible techniques you can employ and how the authors classified techniques based on relative strengths such as objective vs. subjective, etc. This allows you to select the best approach based on the degree of precision you are willing to accept and your goals.
Chapter five, identification of IT costs, is about what we all struggle with: identifying total costs of ownership, finding the "buckets" into with to place the costs, and the cost drivers themselves. The costs are divided into direct and indirect cost portfolios, and the cost breakdowns for each portfolio are comprehensive. This material is valuable and will lend itself nicely to a number of approaches, among them activity-based cost management. Chapter six, IT Cost Control, shows you how to manage the costs that you identify and is a good primer on IT budget management for those who find themselves in a new management position.
IT Business Case Accounting, the topic in chapter seven, presents a straightforward approach to building your business case for IT investments. This is "must" reading for IT management and consultants. Chapter eight, Risk Analysis, is standard fare if you are familiar with these techniques. It is covered completely and provides a solid foundation in the science of identifying, quantifying and managing risks.
My favorite chapter is nine, Evaluation of the IT Function. As a consultant who performs such evaluations I thought I knew a thing or two. This chapter sparked some ideas, and the accompanying checklists are worth their weight in gold. Not only is there a comprehensive set of checklists, you are also shown how to assess the results. Contrast this with books (and consultants) who provide findings, but fail to show the root causes of the findings or make valid recommendations based upon them.
Chapters ten, eleven and twelve tie up some loose ends by covering Ranking and Scoring of the evaluations, Determining Value for Money, and Designing IT Surveys for Benefit Measurement. Taken together these three chapters can stand alone as a small book on using quantitative methods to measure IT value. Chapter thirteen addressed project management issues, which were fairly generic, and the authors end the book with a chapter on final thoughts. They include nine appendices, of which the following provide additional value: C - Financial Measurements used in Cost Benefit Analysis (great primer for non-financial types), D- Factor Analysis (advanced techniques for correlating questionnaire responses), E- Sample Sizing Scenarios (how to select sample size using statistical techniques), F through H Questionnaires and associated issues (the questionnaires are more excellent material for consultants and auditors).
This book provides a roadmap to measuring and managing IT benefits. The approach is straightforward and the goals are achievable (although not without a lot of hard work). It also provides many valuable checklists that will serve you well regardless of whether you are intent on implementing a measurement and management program, or are just seeking some techniques to more effectively manage an IT function. I strongly recommend this book to all consultants who perform IT organizational analysis, and members of IT governance committees or program management offices.
The core of the approach is active benefit realization (ABR), which is a continuous assessment and management methodology that is characterized by: (1) self-calibration/continuous improvement, (2) IS/IT management by all stakeholders (technical and business), and comprehensive understanding of IS/IT and how it supports business functions and processes.
ABR is immediately introduced in the beginning of the book, as well as why the approach is critical to fully integrating IS/IT into the enterprise as a business enabler. The next part of the book discusses key factors for evaluating information systems. This part is rich with checklists, tables and other useful artifacts. Building upon this foundation is excellent material on evaluation techniques, outcomes and benefit modelling (taking an investment-oriented approach that is one of the best applications and services portfolio management approaches I have come across), and the details of micro modelling (the devil, they say, is in the details!)
Once the foundation has been built the book presents the ABR approach as a process. In simplistic terms this process entails three phases: (1) Setting the course (capturing and understanding the business, financial and project views), (2) Formative evaluation (stakeholder management of the project - this approach is nearly identical to the approach prescribed by PRINCE2, which is the U.K. project management standard), (3) Moving forward (continuous improvement and calibration. In other words, consolidating gains and improving upon them in a methodical manner.) The last part of the book is a collection of tips, tricks and traps - this is essential reading and contains the collective wisdom of the authors. Heed every word because there are some real gems here.
I learned a lot from the book, including many standalone techniques for analysis, evaluation and financial assessment that I can use on other projects. As a whole, the approach embodied in ABR is sound and one that I will use on my next engagement that requires an in-depth analysis and formulation of a strategy, assuming of course, that the next client has a strong commitment to follow the course of action set forth in the book. The benefits of ABR certainly will provide a handsome return on the investment and commitment required to make it a success. This book is invaluable and highly recommended for consultants, CIOs and upper IS/IT management. It is also highly recommended for any project team operating under PRINCE2.