I’ve touched on the need for IT innovation before in previous blog posts (here and here). But, what about software development? How can a CIO change the typical process of developing software?
Zelijko Obrenovic, of the Software Improvement Group, is tackling that question with a new Java-based tool he’s created, Sketchlet, which aims to empower engineers and non-engineers in spending more time considering alternative ideas before proceeding with engineering.
It’s an interesting – and innovative – concept, given that developers often engineer wrong products due to poorly defined requirements and miscommunication. This tool would empower engineers to explore a variety of designs and options before selecting the best one, promoting creativity and trial by error – and also allowing those involved to more thoroughly consider user issues and hardware and software possibilities.
This is the type of forward thinking that IT often doesn’t have time for. Yes, changes such as these would require a cultural shift within an organization, but that change in culture could bring about an enhanced process for creating software and a better end product, benefiting IT and the business.
The CIO is responsible for doing more than keeping IT running, he or she is responsible for driving IT forward and for trying new ideas that could have a valuable impact on the organization. Sketchlet exemplifies the type of thinking that is required of a CIO, not just with development, but with every aspect of IT, from budget management to outsourcing.
What new ideas have you tried lately for the sake of innovation?
Download the article, “Software Sketchifying: Bringing Innovation into Software Development,” from IEEE Software.