Craftsmen don't want to focus on methodologies; craftsmen want to be left alone to practice their craft. That's not to say there aren't methodologies that would be helpful for programmers; but I would expect them to develop and spread quietly through forums and word-of-mouth in the same way software improvements do, not through flashy marketing campaigns and company-wide rollouts.
It's management that spends time thinking about methodologies, because tweaking methodologies is a major way management justifies its existence. I've seen management switch from salaried employees to contractors (and then back again a couple years later); from cubicles to open rooms to offices to cubicles; from email communications between team members to instant messenger to frequent personal meetings. I've seen management declare that all new software would be written in a certain language for maximum efficiency (in this case, Java, for the hope of "replaceable cogs" that I mentioned before). In every case, management insisted these changes would be critical for making everyone's job easier and raising productivity. In every case the programmers rolled their eyes and did their best to ignore it and get on with programming.
So if you're saying programmers are excited about this particular methodology and are pushing it forward, while managers aren't interested in it....well, I guess there's a first time for everything.
Available for small or large Perl jobs and *nix system administration; see my home node.