[externalreality]

The first problem with agile is that false dichotomy - "It's either agile or waterfall". Sorry but that dichotomy doesn't exist. Waterfall vs Agile is just a good-bad binary. Surely you want to iterate quickly and stay in constant contact with customers, if that is all agile is then I am all in. However, I can't subscribe to robbing developers of ownership of a domain. I would even do microservice arch if it meant dividing things up into domains and assigning developers microservices that they own. I want to keep developers and giving them responsibility and ownership is a good way to do it.

Its funny because, in Agile you hear "You don't want one developer leaving with all the knowledge" now instead we have all the developers leaving with all the knowledge.

[jay_kyburz]

Nothing in the Agile Manifesto says anything about robbing developers of ownership of a domain. The first line of the manifesto is "Individuals and interactions over processes and tools", which suggested to me that individual work satisfaction is right there at the top.

Whoever is running your team is doing it wrong.

[externalreality]

I wouldn't hang on every word of the agile manifesto. For example you don't have to google too much before you find people having debates over unit testing vs acceptance testing in the name of being "Agile" not giving to much attention to the "over processes and tools" part of the manifesto.

[jay_kyburz]

If we are going to critique Agile I think we should first agree what Agile is. Agile is the manifesto, not what some random dudes on the internet say it is.

[externalreality]

Agile is not the manifesto, I has really never been. Agile does not have a real definition.