Select the directory option from the above "Directory" header!

Menu
INSIGHT: Top 10 ways IT decision makers can become agile

INSIGHT: Top 10 ways IT decision makers can become agile

“Done badly, agile development will create a lot more problems than it solves."

CIOs and IT decision make are under pressure to support fast-evolving digital business scenarios but are finding traditional project and development methods unsuitable.

That’s according to Gartner, which claims enterprises are increasingly turning to agile development to speed up projects and illustrate their value.

Speaking ahead of the Gartner Application Architecture, Development and Integration Summit in Sydney this month, Nathan Wilson, research director at Gartner, claims that when executed well, use of agile methods has the capability to transform IT-business relationships and have a major positive impact on IT value delivery.

However, the value will be delivered only if the CIO and the entire IT management team are dedicated to the culture change that is necessary for success.

“Done well, agile development can be an integral part of the portfolio of methods that the CIO uses to deal with increasing business demand for innovation," Wilson says.

“Done badly, agile development will create a lot more problems than it solves."

Gartner has identified 10 guiding principles for agile development:

No. 1: Agile is not one thing

Agile development methodologies are a set of approaches to software development that share a common philosophy but are sharply distinguished in the details of their implementations.

They therefore tend to be adapted to different sorts of problems. Sophisticated organisations with a lot of experience may well use more than one of these approaches, but an organisation that is getting started should select one approach and master it before attempting other approaches.

No. 2: Agile is not a "pick'n mix" methodology

Agile methods are highly systematic. Every component element of the methodology is crucial to the success of the methodology.

A common mistake is for an organisation to embrace some elements of an agile methodology, such as the sprint, but to ignore or play down other elements, such as managing "technical debt."

Such organisations enjoy the kudos that comes from rapid development and release of new code, but they are storing up trouble by failing to address technical debt.

No. 3: Embracing agile is a joint business-IT activity

The full benefits of agile cannot be achieved without engaging with business leaders, management and the user community. If the rest of the business does not have an immediate appetite for working in a new way, careful planning and communication will be needed to bring different communities of managers and users on board.

No. 4: With agile, it is important to walk before you try running

Experienced agile practitioners can tackle large-scale developments - the equivalent of climbing Mount Everest. But it takes many years to develop the necessary skills to be able to take on such large-scale software projects.

Any organisation that is starting out on the agile journey needs to start in the foothills to develop the confidence and competence to take on larger tasks.


Follow Us

Join the newsletter!

Or

Sign up to gain exclusive access to email subscriptions, event invitations, competitions, giveaways, and much more.

Membership is free, and your security and privacy remain protected. View our privacy policy before signing up.

Error: Please check your email address.

Tags Gartner

Show Comments