people will see 'Agile' or 'sprint' and cringe.
Agile has been so oversold, theres a big backlash against it coming....
I'll be very surprised if we actually go back to merging, integrating, testing, and releasing code once every few months/years instead of hours/days.
And many firms do continuous delivery for very critical products and services without using Agile nor anything even remotely like Agile.
1. Customer satisfaction by early and continuous delivery of valuable software
3. Working software is delivered frequently (weeks rather than months)
4. Close, daily cooperation between business people and developers
5. Working software is the principal measure of progress
[1] https://en.wikipedia.org/wiki/Agile_software_development#The...
In fact, the only parts of it orthogonal to continuous delivery are
5. Projects are built around motivated individuals, who should be trusted
6. Face-to-face conversation is the best form of communication (co-location)
9. Continuous attention to technical excellence and good design
10. Simplicity—the art of maximizing the amount of work not done—is essential
11. Best architectures, requirements, and designs emerge from self-organizing teams
12. Regularly, the team reflects on how to become more effective, and adjusts accordingly
And aside from (maybe) embracing remote work, I don't see those things going away anytime soon. I certainly wouldn't want to work somewhere that rejects them.
We could stand to lose the name, but probably not the ideas.
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
All of those strongly point towards continuous delivery being part of agile. Continuous delivery is also a given in XP, one of (if not the) founding agile methodology.
I think you need to dilute agile quite a lot to release once a year, although I daresay you can.
