Agile's Successor: Continuous Delivery - 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.

IT Leadership // Enterprise Agility

Agile's Successor: Continuous Delivery

Traditional Agile methods have evolved quickly to address current programming needs. Continuous delivery mixed with select Agile practices equals the preferred way forward.

The celebration of the tenth anniversary of the Agile Manifesto three years ago brought to light a curious aspect: The methodologies of Agile are so mainstream that they are largely taken for granted. Only organizations that are firmly committed to other paths do not default to the modern practices of Agility -- the embrace of change; the coding in short sprints; the frequent, automated testing; and short feedback loops, both from the process itself and from the customer.

The success of Agile in advancing software development so much in such a short period of time is nothing short of spectacular. Agile techniques now seem so natural and intuitively obvious that many developers cannot recall how software could have been developed other than via Agile approaches. So marches progress.

However, it's becoming clear that Agile alone is no longer sufficient to keep up with the demands of the present day. This deficiency is due in part to the fact that it was formulated to address older needs, especially the inability of projects to adapt to changing customer requirements.

Today, however, software complexity and the need for constant updates are making it difficult for leading edge organizations to keep up without moving beyond Agile and embracing continuous delivery (CD). Unlike its immediate forebear, continuous integration, the two words "continuous delivery" mean exactly what they appear to mean: a process -- or more accurately a project pipeline -- that constantly generates a deployable, tested product, even if feature-incomplete.

Read the rest of this article on Dr. Dobb's.

Prior to joining Dr. Dobb's Journal, Andrew Binstock worked as a technology analyst, as well as a columnist for SD Times, a reviewer for InfoWorld, and the editor of UNIX Review. Before that, he was a senior manager at Price Waterhouse. He began his career in software ... View Full Bio

We welcome your comments on this topic on our social media channels, or [contact us directly] with questions about the site.
Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
Charlie Babcock
Charlie Babcock,
User Rank: Author
9/18/2014 | 10:03:03 PM
10 years since the manifesto?
I didn't realize 10 years have passed since the Agile Manifesto. Andrew is right, Agile development must be tied into continuous delivery, or it loses much of its value. And both must be tied into a cloud or cloud-like infrastructure to yield their full value.
2021 Outlook: Tackling Cloud Transformation Choices
Joao-Pierre S. Ruth, Senior Writer,  1/4/2021
Enterprise IT Leaders Face Two Paths to AI
Jessica Davis, Senior Editor, Enterprise Apps,  12/23/2020
10 IT Trends to Watch for in 2021
Cynthia Harvey, Freelance Journalist, InformationWeek,  12/22/2020
White Papers
Register for InformationWeek Newsletters
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you.
Flash Poll