Just quickly picking up on the DNA thread. If you remember I was building quite a basic picture of what happens in a ‘typical week’ on the average IT service desk. It was really an exercise to see how people cope with the balance of planned/unplanned activities and how cloud computing may (will ) have an impact to such activities.
You may recall my wrap up picture of the Monday to Friday DNA week.
As depicted above I tried to ring fence low level tasks that may be replaced/amended/affected by a cloud strategy. It was desperately basic and lacked any real methodology or plan. However, I knew that and wanted to start right at the ground level on the KISS premise. For sure we can all make things complicated quickly!
Pushing this forward I stumbled upon ( or someone suggested ) an excellent paper from IBM entitled The Future of the IT Department. Visit http://www.ibm.com/cloud-computing/us/en/
The argument IBM makes is that at some point the advent of cloud will demand a change to how the overall IT Department will function and deliver service. All this is music to my ears of course because it has got my juices flowing again on the risk of standing still in the IT Service aspect of IT delivery. Of course it is a tough one to know what to do because there are few experts out there and all the traditional models we had before are potentially redundant. I therefore like the IBM patented Component Business Model for the Business of IT. Yes IT service is a business and not just a function residing in the dungeon of a back office cost overhead.
So originally i had started looking at just the IT service fulfillment aspect from the lens of the traditional service desk but the IBM report has made me look a lot wider to how the cloud journey is going to change the IT department landscape.
Graphically they have a framework to establish the IT department structures and functions both BEFORE and AFTER
I wasn’t planning to throw any thesis at you in this blog because IBM have done a pretty dam good job IMHO but I would like to see if anyone has any views on the approach to break down an IT department’s functions and services into components as suggested by IBM. I suspect for many they do not and have a much more one dimensional view of the IT department i.e. Development, Support, Operations, Security, Architects. I think that to really get into the cloud impact assessment a much more three dimensional and deeper analysis is needed and the IBM Model is a great resource to look at how you can get there.
As always any comments for or against would be helpful.