IMO the problem with software methodologies is leaky abstraction.
There just isn't a general framework that tells you how to categorize and deal with every issue that you come up with.
The main thing I get from the various methodologies is general philosophies. Things like "try to get feedback incorporated quickly". Or "Identify in advance the things that are expensive to change".
I kind of wish we applied "micro-methodologies" rather than methodologies. I think we should be doing "import retrospectives" rather than "import scrum" and sharing and experimenting with a diversity of approaches (e.g. various different ways to do retros).
We're essentially treating "methodologies" as software that runs teams. Furthermore, if we are doing software we should follow the UNIX philosophy and the bazaar rather than the cathedral.
Software in the abstract problem solving against varying constraints. It stands to reason there would not be a single method that capture the best means of doing so.
There just isn't a general framework that tells you how to categorize and deal with every issue that you come up with.
The main thing I get from the various methodologies is general philosophies. Things like "try to get feedback incorporated quickly". Or "Identify in advance the things that are expensive to change".