topleft
topright
Enter the Member Network Zone View the Top 10 Points Leaderboard View Members Who Are Currently Online View Latest Member Activity

Featured Members


Member Network Zone

Expert Blog Comments

The Trouble with Big IT
Hello All, "Intentionally confusing" is right. As a company that cuts through the hype and overstat...
Google App Store Open for Business
I will be keeping an eye on this, it does not seem like Google fails at much but I have yet to be ov...
State Updates Extortion Laws to Cover Identifiable Info
Hopefully, common sense changes like these will become part of every states laws. Unfortunately, the...
HP Tries On a New Brand Image: ‘Let’s Do Amazing’
I like it. It's a good counter to IBM's Smarter Planet campaign, which really captured the idea that...
The Trouble with Big IT
Michael - In reading this I kept going back to an IT project risk model that I know of as coming vi...
Six Steps to Improve the Odds of IT Success Print E-mail
User Rating: / 0
PoorBest 
Monday, 01 June 2009

How do organizations create a responsive IT strategy and improve the success of IT projects that are focused on agility and innovation? Former Network Services Co. CIO Michael Hugos emphasizes six key factors:


Only automate routine business operations. Eighty-to-ninety percent of business activities fall into the routine category, says Hugos, and that is where IT should focus its automating efforts for efficiency and low cost. Unique or non-routine activities change quickly and are best handled by people.


Maximize the use of IT you already have. Develop new systems by leveraging capabilities and features of existing systems. This can be achieved, Hugos says, by building data links between existing systems and creating simple user interfaces that blend together functions in existing systems.


Utilize technologies that enable agile IT. Take advantage of the technologies that will help create responsive organizations, such as: server virtualization; cloud computing; software as a service; services oriented architecture; mashups; and agile IT system development.


Empower your people. Provide the training to give people the skills they need to do their job, give them clear direction on the objectives to be accomplished, free them up to find the right solutions on their own, then reward the team when the work is done. Resist the urge to tell people how to do their jobs: Coordination works, control doesn't.


Have a separate project office. This allows the CIO to get regular project status reports without disrupting the development teams from the work they are doing.


Provide 80% solutions. To capitalize on business opportunities before the profit margins dip, the scope and focus of an agile IT solution should be limited. Don't try to address all the issues or you'll end up with scope creep. Eighty percent solutions are agile, 100% solutions let others pass you by. Focus on the here and now and do less analysis, says Hugos.




Comments (1)
RSS comments
1. 06-01-2009 14:16
 
While these principles make a great deal of sense, organizations must realize that embracing technologies that enable agile IT - like SOA or mashups - require dedicated time and investment to determine how these solutions need to be architected. One doesn't spring from relying on data centers with terabytes of storage to leveraging Amazon EC2 overnight. This friction between the desire to use new technology and recognizing the effort required to do so is often one of the pitfalls of adoption, but worth the effort if entered with eyes wide open.
Registered
 
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it

Only registered users can write comments.
Please login or register.

 
< Previous   Next >




CIOZone Poll

Which of these IT initiatives are you green-lighting in 2010 after delaying last year?
 

News & Noteworthy Archive

Past News Items From Reuters

White Paper Library