What is required is shades of grey. Here is a simple example.

Lets say our team's methodology includes documenting code changes.

Some commits should require API Documentation updates, e-mails to the entire team, an entire separate document about the changes.

Other commits may only need a short comment like "removed extra whitespace"

Fallacy of the grey. Yes, a good team will be better than a bad team for any reasonable methodology. That doesn't mean there aren't methodologies that are better than others.

I don't disagree, but I don't think that becoming more Agile* is necessarily always a very good methodology.

*(capital A, for what it has become at the hands of process consultants rather than what was intended originally)