Technology That Every CIO Needs to Know About
- How CIOs Can Stay On Top of the Changes in the Technology That Powers the Company
- Narrated by: Jim Anderson
- Length: 1 hr and 9 mins
- Unabridged Audiobook
- Release date: 12-05-14
- Language: English
- Publisher: Blue Elephant Consulting
Regular price: $6.95
Buy Now with 1 Credit
Buy Now for $6.95
As the CIO you need to be understand how to pick the correct type of database to be used on projects. You need to watch the rollout of other large-scale IT projects and learn from them: what went right and what went wrong.
What You'll Find Inside:
The Seven Stages of Big Data Analytics That Every CIO Needs to Know About
CIOs Need to Plan for the End of a Cloud Relationship
Why CIOs Need to Get Good at Reusing Technology
When It Comes to Data Mining, Is the CIO in Charge?
The IT world that we live in these days seems to be awash in big data. As the CIO you are going to be called on to make important decisions about how your firm handles its own big data issues. You'll need to pick the right solutions and ensure that you are not being locked into proprietary vendor solutions.
It seems as though every firm is in the process of moving more and more of their computing into "the cloud". As the CIO it's going to be your responsibility to make sure that you have a plan for how you want to handle your cloud vendor at the start of the relationship as well as at the end of it.
The value of the IT department to the rest of the company becomes apparent when other departments need your help in sifting through vast quantities of data. Make sure that you have a plan for how you are going to do this. Also make sure that you have a help desk that is going to be ready to provide your customers with the support that they'll need.
Customer ReviewsMost Helpful
By LindsayR on 12-31-14
Interesting but cursory
I am not a CIO, but it's hard to get a decent survey of transformative technologies outside my own area. The topics addressed in this short overview were relevant and interesting but I was disappointed by some of the chapters which provided little to know case studies or examples of how the mentioned technologies could be used well or poorly. For example, the author warns against proprietary solutions masquerading as standards, but cites no examples.
Where case studies are mentioned, though, they are good.