tbh, Agile as preached and Agile as practiced is not exactly similar.
I think there is even a good video describing that, from 7 years ago[0].
agile does not at all mean backlogs, or sprints, or specific tooling or even CI. Agile boils down in essence to “deliver often, do the minimum needed, prioritise prototyping”.
"Manifesto for Half-Arsed Agile Software Development
We have heard about new ways of developing software by
paying consultants and reading Gartner reports. Through
this we have been told to value:
Individuals and interactions over processes and tools and we have mandatory processes and tools to control how those
individuals (we prefer the term ‘resources’) interact
Working software over comprehensive documentation as long as that software is comprehensively documented
Customer collaboration over contract negotiation within the boundaries of strict contracts, of course, and subject to rigorous change control
Responding to change over following a plan provided a detailed plan is in place to respond to the change, and it is followed precisely
That is, while the items on the left sound nice in theory, we’re an enterprise company, and there’s no way we’re letting go of the items on the right."
What methodology do you find in Agile? It doesn't really say much. In fact, here is the Agile Manifesto in full:
--
* Individuals and interactions over processes and tools
* Working software over comprehensive documentation
* Customer collaboration over contract negotiation
* Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
--
If anything, Agile promotes not getting hung up on methodology, to just use some common sense.