How To Become More Agile and Innovative - InformationWeek

InformationWeek is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Government // Mobile & Wireless
02:02 PM
Jim Ditmore
Jim Ditmore

How To Become More Agile and Innovative

It's time to move beyond the latest agility and innovation fads and institute substantive approaches. Here's how IT can get involved.

Executives are more determined than ever to make their elephant organizations dance. With increasing frequency in companies around the world, they speak of the need for "agility" and "innovation."

Even companies with a solid history of developing new products feel under pressure to show they're capable of innovating at a rapid pace. Take Procter & Gamble, which in a recent statement following its soft financial results talked about "increasing our agility, improving cost efficiencies, improving our speed to market, and relentlessly focusing on innovation in every part of our business." Perhaps this widespread urgency can be chalked up to the recent demises of Kodak, Borders, and other companies.

But applying the latest management technique is a bit like going on a fad diet. It may yield short-term improvements, but it likely won't deliver a sustainable advantage. Let's focus here on more substantive approaches and map out how IT management should respond to business needs to increase agility and innovation.

Let's start with agility. The latest agility fad is the "standing meeting," said to be a surefire way to accelerate decision-making. This approach is derived from agile software development, with its incremental delivery streams, frequent, even daily, turnarounds, and tight feedback loops. Rather than make the leap to apply agile project practices to how the business is run, instead use agile judiciously. From my experience, agile methods are best utilized when:

-- requirements, particularly user interfaces, aren't well defined or likely to be fluid.

-- a rapid turnaround or incremental delivery provide a significant market advantage.

-- the business process will be changed and improved in tandem with the system development.

A good rule of thumb for the typical IT shop is to leverage agile development for at least half of your small to midsize software projects and at least a quarter of your large projects. But remember: Agile is a build methodology, not a run methodology. Apply a mix of lean and capability maturity model (CMM) approaches to your run functions. Treat these run activities as the factory that they are (or should be). Successful run approaches emphasize process definition, metrics, robust execution, a high degree of analysis, and incremental process improvements.

Global CIO
Global CIOs: A Site Just For You
Visit InformationWeek's Global CIO -- our online community and information resource for CIOs operating in the global economy.
Another area where companies can substantially improve agility and time to market is management approvals. If you pull the cycle time for just about any routine company transaction (paying expenses, provisioning new servers, etc.), you'll find that management approvals take up 25% to even 40% or 50% of the total time. Why? Because most companies have myriad approval processes, all done differently, many with manual or cumbersome interfaces and incomplete information.

Reduce this oft-neglected bureaucracy by investing in an intranet manager approval page, one portal where a manager can see what requires his or her approval and either approve it directly or easily link to the appropriate page. Modern workflow systems let HR, finance, and other departments set approval (or rejection) time service-level agreements for all managers. These investments will speed up dozens of company processes affecting most employees, and set an agile pace.

Also slowing down most companies are their processes for defining system requirements. Requirements, either poorly designed at the outset or improperly constructed after multiple, elongated sessions, are a likely cause of significant defects and serious project delays. Excellent requirements management tools, such as IBM's RequisitePro and Borland's Caliber, can improve your definition time and quality. Also, work with your partners to ensure there's enough expert staff (business and technical) dedicated to timely completion of the requirements. Use proven best practices such as Rapid Requirements to gain further advantage.

Moving on to innovation, what are some of the ways that you as an IT leader can contribute?

We welcome your comments on this topic on our social media channels, or [contact us directly] with questions about the site.
1 of 2
Comment  | 
Print  | 
More Insights
InformationWeek Is Getting an Upgrade!

Find out more about our plans to improve the look, functionality, and performance of the InformationWeek site in the coming months.

10 Things Your Artificial Intelligence Initiative Needs to Succeed
Lisa Morgan, Freelance Writer,  4/20/2021
Tech Spending Climbs as Digital Business Initiatives Grow
Jessica Davis, Senior Editor, Enterprise Apps,  4/22/2021
Optimizing the CIO and CFO Relationship
Mary E. Shacklett, Mary E. Shacklett,  4/13/2021
White Papers
Register for InformationWeek Newsletters
Current Issue
Planning Your Digital Transformation Roadmap
Download this report to learn about the latest technologies and best practices or ensuring a successful transition from outdated business transformation tactics.
Flash Poll