DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
  1. DZone
  2. Testing, Deployment, and Maintenance
  3. DevOps and CI/CD
  4. Has Continuous Delivery Replaced Agile?

Has Continuous Delivery Replaced Agile?

Many teams claim to be “Agile” as a way to excuse lack of visibility, lack of planning and by individuals who don’t have a particularly deep experience shipping software at scale.

Yaniv Yehuda user avatar by
Yaniv Yehuda
·
May. 12, 16 · Opinion
Like (4)
Save
Tweet
Share
3.38K Views

Join the DZone community and get the full member experience.

Join For Free

miko from gradle has become the latest to eulogize agile in a controversial blog he posted last week.

he makes the argument that agile’s death was an untimely one, brought about by years of neglect and abuse. miko says that “the word agile has come to be somewhat meaningless, which is why it’s time to move on from it.” so many development teams for lack of a better word claim to be “agile” and in some ways it’s often used as a way to excuse lack of visibility, lack of planning and by individuals who haven’t read the agile manifesto or don’t have a particularly deep experience shipping software at scale. so when a word loses all meaning, it’s time to move on.

“now that agile is dead,” he continues tongue in cheek “we got to see how many people come to the funeral of agile.” agile meant so many different things to so many different people, but agile didn’t have very much sponsorship in the executive suite. agile was a collection of essentially rebellious methodologies, and what agile rebelled against was worthy for its time, and agile did its job to topple the tyranny of waterfall software development. but waterfall died many years ago, and so the rebellious core of agile didn’t produce the expected freedom by itself.

so how does miko suggest we move forward as an industry in the aftermath?

the paradigm of “continuous delivery (cd)” seems to be the logical successor to agile according the miko. continuous delivery provides an umbrella term that does not specify methodology–and doesn’t require much of a manifesto. everything you need to know is in the title–you just deliver shippable software in as continuous of a way as possible. this allows a team to pull whichever agile principles and methods needed in order to achieve that goal. this addresses one of the complaints of agile, which is that it became a religious movement with gurus–and that these highly paid agile gurus would come with one-size-fits-all solutions for development teams which were hard to realistically fit to real-world development.

miko goes on to explain the difference between “agile” and “continuous delivery” as follows:

the thing that has shifted most materially to support the need for a new term is the tooling. agile tooling was mostly focused on human productivity and were based on shuffling trello cards and the like. the age of continuous delivery is now being ushered in with a recognition that we are now squarely in the age of devops.

i found the essay to be some good food for thought and while arguments can definitely be made on some of the points, i think we can all agree that there are lessons here in how we must utilize the latest trends in the industry.

agile Continuous Integration/Deployment Delivery (commerce)

Published at DZone with permission of Yaniv Yehuda, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Why Every Fintech Company Needs DevOps
  • Beginners’ Guide to Run a Linux Server Securely
  • Java Development Trends 2023
  • Spring Cloud: How To Deal With Microservice Configuration (Part 1)

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: