How do you assess technology risk? When do you assess it? There's plenty of methodologies that do this and I've linked to a several documents below, one a risk assessment toolkit authored by the State of California CIO Michele Robinson and another NIST guidelines for assessing technology risk.
"We don't start or lead with technology. We lead with "what is the business outcome that we are trying to drive towards"," says HP Software CIO Paul Chapman. With that, Chapman and CIO strategic advisor Tim Crawford riff on why IT leaders need to focus on people as much as they do on process and technology.
It's that time again when I make my forecasts for the new year. Sometimes, my predictions work out, sometimes not. Here's 10 topics that will be front and center for CIOs in 2014. What do you think I overlooked? Anyway, here goes.
While legal and technical aspects of the cloud journey are important, the first consideration is what will run on that cloud.
Recently, I was presenting to the IT strategy team of a large enterprise. I talked about the journey to cloud, what are the things you should review and what decisions should you take. Very quickly, the discussion boiled down to technology and legal aspects.
A good year ago I was in Quebec, and let me disclose something here … speaking French, I’m really welcome out there. We had a wonderful time. One of the customers we met was a local bank. Their IT team wanted to experiment with cloud and we convinced them that cloud enabling their development environment made a lot of sense.
Over the last couple months, the same discussion keeps popping up over and over again. It started last August at a cloud introduction workshop I ran for an insurance company. I talked about the need to manage the service portfolio and highlighted the importance of a proper governance between business and IT. One of the attendees complained that the business had no understanding of the cost associated with the development of new services.