Perhaps you're too passionate for your own good ;-)

Seriously, most of the people I've worked with simply aren't that passionate. Process changes come and process changes go, and very few of us say anything. Agile was introduced by a Big Important Person in my previous position, and, it was basically ignored by management. Oh, not in public, but when us peons asked about adopting some of agile's strengths, management basically said nothing was going to change. Very little complaint.

My new position is in a team that is allegedly using Agile. Well, iterations anyway. "Short" might be stretching it a bit too far as a descriptor, though - I think my current iteration is somewhere around a month, with future iterations scheduled for 2 weeks each. And their contents have been determined by management, not development. Most developers seem to be just doing what they're told rather than driving for improvement.

And I can really understand where they come from. Keep your head from poking up, and raising ire (I don't seem to care much about that, which gets me in trouble, both good and bad), get your job done, go home. And pray that they don't change the rules again. Focus on what's important, and for most people, that's not the software. It's the family. Choose your battles wisely, and apparently lots of people have enough battles at home to concern themselves with the battles at work.

For too many companies, management is about power, not wisdom. And if they allow developers to pick the process methodology, that's like conceding power, and thus inherently counter-productive (to their personal power-base growth). If you find an employer where management is about wisdom, not power, let me know. Especially if they're hiring.