IT Risk mobi 下载 网盘 caj lrf pdf txt 阿里云

By M. McDonald (Chicago, IL United States) - See all my reviews

IT used to be thought of as separate from the business, a staff function that by itself could enable but not change the business, its value or its brand. Well that view no longer holds water and Westerman and Hunter show how IT risk is really business risk and needs to be treated as such. In their book, the two provide a clear and concise discussion about IT risk from the perspective of the leader/practioner rather than the perspective of the auditor.

Since business and IT have become so closely intertwined and this book offers clear and actionable advice - not fear, uncertainty or doubt - I recommend this as a read for the CIO/IT executive as well as the CEO so they can understand what to expect both in terms of protection but also competitive advantage from the ability to manage IT risks.

I come to this position from the way Westerman and Hunter introduce the concept of risk management and the way they have ***anized the book. They introduce a framework of four "A's" that looks at risk from a business perspective, rather than an auditing or compliance perspective. The four A's that define IT risk are:

Availability -- keeping business processes and information flowing through the business

Access -- ensuring that the appropriate people, including customers and suppliers, can get the information and functionality they need to be effective

Accuracy -- concentrating on providing timely and complete information to meet operating and oversight needs

Agility -- the ability to change with managed cost and speed.

Westerman and Hunter address this subject in a clean and concise nine chapters that provide actionable advices on how to plan and manage risks. One thing of note is that the book talks about using your risk management capability as a competitive weapon -- what you can do that others cannot because you manage risk better. This gives the topic of risk management a strategic context that is unique to this work.

The book can be thought of as being in three parts.

Part One is about the framework and the overall approach to risk management. It includes the following chapters:

Chapter 1: The 4A Risk Management Framework

Chapter 2: The Three Core Disciplines of IT Risk Management

Part Two concentrates on the actionable management steps business and technology executives can use to manage risk.

Chapter 3: Fixing the Foundation: strengthening the base of the pyramid -- about the importance of infrastructure in risk management.

Chapter 4: Fixing the Foundation: simplifying the base of the pyramid -- about how complexity drives risk, cost and performance levels.

Chapter 5: Developing the Risk Governance Process -- covering how do you manage and make decisi*** regarding IT and Business risks.

Chapter 6: Building a risk-aware culture-- here the authors make an important connection between risk and culture and a critical distinction between being risk aware (strategically important) and being risk adverse (strategic killer)

Chapter 7: Bringing the three disciplines up to speed -- concentrates on the program and patterns for effective implementation.

Part Three looks at the future and improvements to risk management

Chapter 8: Looking ahead -- talks about how to incorporate risk management as a positive force in planning and strategy setting

Chapter 9: Ten ways executives can improve IT risk Management.

Overall this is a must read for CIOs, IT risk management and IT profesionals. It is also recommended reading for CEOs and others who want to understand how to manage IT and how to gain advantage from having good IT.

By James Taylor "Enterprise Decision Management ... (Palo Alto, C***SA) - See all my reviews

I was lucky enough to get a pre-release copy of IT Risk: Turning Business Threats into Competitive Advantage by Ge***e Westerman and Richard Hunter. The book approaches IT risk not as a technical issue but as a business and management one with potentially serious c***equences. As businesses increasingly are there information systems, this point of view is both necessary and valuable. The book introduces IT risk and its c***equences, discusses the authors' 4A framework and outlines 3 core disciplines for IT risk management. It then drills into actual steps to take to fix the foundation, develop risk governance processes and establishing a risk aware culture. It wraps up with some forward looking thoughts and a list of ways in which executives can improve IT risk management.

Their basic premise is that effective IT governance essential in times of high change and increasing complexity (of systems as well as of business/problems). They discuss 4As - availability of systems, access to systems and data, accuracy or data and results, and agility in terms of ease of change - as being the framework for risk management. These 4As are ***ed by a foundation, a risk management process and a risk aware culture. The framework and the disciplines mostly work well for the authors, only occasionally becoming confusing to the reader. From my perspective I found the focus on agility very interesting as possible changes to systems should be c***idered along with general IT effectiveness when managing risk. Also, while the foundation is lower level than I usually c***ider, I think the objectives for the foundation can all be met more easily by and ***anization that has adopted enterprise decision management - the approach discussed in Smart Enough Systems: How to Deliver Competitive Advantage by Automating Hidden Decisi***. It can make it easier to assess risk, easier to maintain systems, easier to change and fix them. It can also make it easier to apply risk assessments in operational systems by calling out the decisi*** that must be made, which is where risk assessment matters.

Fixing the foundation is described as a journey and I really liked the focus on incremental improvement. The foundation is a problem as most companies developed their IT infrastructure in stages. However, a poor foundation undermines agility by degrading the business/IT relati***hip and by *** change to existing systems, to meet changing business needs, hard. While I think there are othe***ays to add agility into existing systems, I do agree with their assertion that you need to change and replace foundation to some extent. They make some fairly good suggesti*** for broad steps you can take and show the kinds of payoffs that come from the capabilities you enable with a better infrastructure. The authors make a critical point when they show how change in infrastructure is IT change while change in applicati*** is business change but most IT departments don't see the difference - they see it all as "system" change *** it harder to manage than necessary. Again, a focus on separate automation and management of decisi*** can help clarify this difference. There is a fair amount of useful discussion in the book about the need for both local and central management to which I would add one more category - where do decisi*** live in your ***anization? Should they be managed locally or centrally? The book outlines both incremental and "big bang" approaches to fixing the foundation and notes that incremental change is slower but surer. The discussion of how legacy application modernization might be business value based or risk based (human resources or technology risk for instance) or both (such as a need to change to *** a new business strategy) was well done. I also really liked their idea of a renewal and reinvestment budget to keep legacy modernization ongoing and they had some great stories about human resources risk coming from retirements and the need to get knowledge out of people's heads and into systems.

The section on a risk governance process was thorough, although I think you need to be careful not to implement all of it blindly, and I liked the focus on broad risk awareness - not "risk-averse" or "risk-pro" just "risk-aware". To *** this idea, IT needs to build systems in a risk-aware way - they need to drive their use of technologies and languages, c***ider the c***equences of a failure to update documentation or code and so on. It occurred to me while reading these secti*** that ***anizati*** c***idering a policy manual for this stuff should also c***ider the value of rules and decision management as a basis for a "policy engine". They had a particularly nice example of a mid-sized company finding its legacy applicati***, and the lack of agility in them, to be a key risk and investing in replacing and upgrading systems to make maintenance and evolution easier and less risky. This kind of agility improvement is something enhanced by a parallel focus on decision management.

The book was a fairly quick read, had lots of useful suggesti*** and some good ways to think about the problem. If you think IT risk matters, you should read this.

暂无相关目录，正在全力查找中！

暂无相关内容，正在全力查找中

暂无出版社相关信息，正在全力查找中！

暂无相关书籍摘录，正在全力查找中！

在线阅读地址：IT Risk在线阅读

在线听书地址：IT Risk在线收听

在线购买地址：IT Risk在线购买

暂无原文赏析，正在全力查找中！

书籍介绍

By M. McDonald (Chicago, IL United States) - See all my reviews

IT used to be thought of as separate from the business, a staff function that by itself could enable but not change the business, its value or its brand. Well that view no longer holds water and Westerman and Hunter show how IT risk is really business risk and needs to be treated as such. In their book, the two provide a clear and concise discussion about IT risk from the perspective of the leader/practioner rather than the perspective of the auditor.

Since business and IT have become so closely intertwined and this book offers clear and actionable advice - not fear, uncertainty or doubt - I recommend this as a read for the CIO/IT executive as well as the CEO so they can understand what to expect both in terms of protection but also competitive advantage from the ability to manage IT risks.

I come to this position from the way Westerman and Hunter introduce the concept of risk management and the way they have ***anized the book. They introduce a framework of four "A's" that looks at risk from a business perspective, rather than an auditing or compliance perspective. The four A's that define IT risk are:

Availability -- keeping business processes and information flowing through the business

Access -- ensuring that the appropriate people, including customers and suppliers, can get the information and functionality they need to be effective

Accuracy -- concentrating on providing timely and complete information to meet operating and oversight needs

Agility -- the ability to change with managed cost and speed.

Westerman and Hunter address this subject in a clean and concise nine chapters that provide actionable advices on how to plan and manage risks. One thing of note is that the book talks about using your risk management capability as a competitive weapon -- what you can do that others cannot because you manage risk better. This gives the topic of risk management a strategic context that is unique to this work.

The book can be thought of as being in three parts.

Part One is about the framework and the overall approach to risk management. It includes the following chapters:

Chapter 1: The 4A Risk Management Framework

Chapter 2: The Three Core Disciplines of IT Risk Management

Part Two concentrates on the actionable management steps business and technology executives can use to manage risk.

Chapter 3: Fixing the Foundation: strengthening the base of the pyramid -- about the importance of infrastructure in risk management.

Chapter 4: Fixing the Foundation: simplifying the base of the pyramid -- about how complexity drives risk, cost and performance levels.

Chapter 5: Developing the Risk Governance Process -- covering how do you manage and make decisi*** regarding IT and Business risks.

Chapter 6: Building a risk-aware culture-- here the authors make an important connection between risk and culture and a critical distinction between being risk aware (strategically important) and being risk adverse (strategic killer)

Chapter 7: Bringing the three disciplines up to speed -- concentrates on the program and patterns for effective implementation.

Part Three looks at the future and improvements to risk management

Chapter 8: Looking ahead -- talks about how to incorporate risk management as a positive force in planning and strategy setting

Chapter 9: Ten ways executives can improve IT risk Management.

Overall this is a must read for CIOs, IT risk management and IT profesionals. It is also recommended reading for CEOs and others who want to understand how to manage IT and how to gain advantage from having good IT.

By James Taylor "Enterprise Decision Management ... (Palo Alto, C***SA) - See all my reviews

I was lucky enough to get a pre-release copy of IT Risk: Turning Business Threats into Competitive Advantage by Ge***e Westerman and Richard Hunter. The book approaches IT risk not as a technical issue but as a business and management one with potentially serious c***equences. As businesses increasingly are there information systems, this point of view is both necessary and valuable. The book introduces IT risk and its c***equences, discusses the authors' 4A framework and outlines 3 core disciplines for IT risk management. It then drills into actual steps to take to fix the foundation, develop risk governance processes and establishing a risk aware culture. It wraps up with some forward looking thoughts and a list of ways in which executives can improve IT risk management.

Their basic premise is that effective IT governance essential in times of high change and increasing complexity (of systems as well as of business/problems). They discuss 4As - availability of systems, access to systems and data, accuracy or data and results, and agility in terms of ease of change - as being the framework for risk management. These 4As are ***ed by a foundation, a risk management process and a risk aware culture. The framework and the disciplines mostly work well for the authors, only occasionally becoming confusing to the reader. From my perspective I found the focus on agility very interesting as possible changes to systems should be c***idered along with general IT effectiveness when managing risk. Also, while the foundation is lower level than I usually c***ider, I think the objectives for the foundation can all be met more easily by and ***anization that has adopted enterprise decision management - the approach discussed in Smart Enough Systems: How to Deliver Competitive Advantage by Automating Hidden Decisi***. It can make it easier to assess risk, easier to maintain systems, easier to change and fix them. It can also make it easier to apply risk assessments in operational systems by calling out the decisi*** that must be made, which is where risk assessment matters.

Fixing the foundation is described as a journey and I really liked the focus on incremental improvement. The foundation is a problem as most companies developed their IT infrastructure in stages. However, a poor foundation undermines agility by degrading the business/IT relati***hip and by *** change to existing systems, to meet changing business needs, hard. While I think there are othe***ays to add agility into existing systems, I do agree with their assertion that you need to change and replace foundation to some extent. They make some fairly good suggesti*** for broad steps you can take and show the kinds of payoffs that come from the capabilities you enable with a better infrastructure. The authors make a critical point when they show how change in infrastructure is IT change while change in applicati*** is business change but most IT departments don't see the difference - they see it all as "system" change *** it harder to manage than necessary. Again, a focus on separate automation and management of decisi*** can help clarify this difference. There is a fair amount of useful discussion in the book about the need for both local and central management to which I would add one more category - where do decisi*** live in your ***anization? Should they be managed locally or centrally? The book outlines both incremental and "big bang" approaches to fixing the foundation and notes that incremental change is slower but surer. The discussion of how legacy application modernization might be business value based or risk based (human resources or technology risk for instance) or both (such as a need to change to *** a new business strategy) was well done. I also really liked their idea of a renewal and reinvestment budget to keep legacy modernization ongoing and they had some great stories about human resources risk coming from retirements and the need to get knowledge out of people's heads and into systems.

The section on a risk governance process was thorough, although I think you need to be careful not to implement all of it blindly, and I liked the focus on broad risk awareness - not "risk-averse" or "risk-pro" just "risk-aware". To *** this idea, IT needs to build systems in a risk-aware way - they need to drive their use of technologies and languages, c***ider the c***equences of a failure to update documentation or code and so on. It occurred to me while reading these secti*** that ***anizati*** c***idering a policy manual for this stuff should also c***ider the value of rules and decision management as a basis for a "policy engine". They had a particularly nice example of a mid-sized company finding its legacy applicati***, and the lack of agility in them, to be a key risk and investing in replacing and upgrading systems to make maintenance and evolution easier and less risky. This kind of agility improvement is something enhanced by a parallel focus on decision management.

The book was a fairly quick read, had lots of useful suggesti*** and some good ways to think about the problem. If you think IT risk matters, you should read this.