XP Is Too Simplistic

Sound familiar? Managers said the same thing, but for a different reason.
XP challenges the perception of developers that no one understands what they
do and can't do it themselves. This is true to some degree. But it shouldn't be true
because of the process they use. XP takes the magic out of process and lets it live in
the code, where it belongs. The magic is in the results.
XP gets out of a developer's way. You produce no unnecessary documentation.
You get to focus on designing and developing good code. You get to enjoy your
time, rather than loathing having to come to work.
XP is not simplistic. It is simple, uncluttered. Some aspects of the discipline
aren't easy for developers (see the discussion of pair programming below), but it has
the best chance of any approach we have ever seen of fostering a rich environment
for programmers.
Often, when an experienced developer says this what they really mean is "I've
learned other ways to do software (which involves little programming) and my
career has advanced because of it. I don't want to go backwards (at least not careerwise).
And besides, I'm not as good at programming as I once was because I spend
most of my time doing higher level things." Very few of these people actually think
the higher level things they do are as fun or that the process they use to do those
higher level things are efficient. They are often scared that what they've gotten good
at will be looked at as less valuable.