The hard thing about Extreme Programming is that it depends on 12 practices, the practices are independent, and some of the practices make management and/or pro

The hard thing about Extreme Programming is that it depends on 12 practices, the practices are independent, and some of the practices make management and/or programmers uncomfortable. The obvious one here is pair programming. Many programmers love pairing and immediately get the value, but many others find it exceedingly uncomfortable - so uncomfortable that they aren't willing to do it. And on the management side, practices like "The customer is always available" are hard to do in practice, as they challenge organizational boundaries. But without pairing, without a customer rep directly integrated into the team, without TDD, without collective ownership, without sustainable pace - it falls apart very quickly. And what do we get instead? Scrum. And not even real Scrum, but the BS pseudo-scrum that is pretty much tv and dessert first for authority-centric management and lazy uncommunicative programmers alike. So how do you pull that off? Well, you hire a bunch of "scrum masters", who are basically just busybodies with no actual authority, to go around pestering people all the time and calling meetings in order to get anything done at all. There's no control, everyone is miserable, old-timers pine for the days of Waterfall, and it just sucks.