Although Kent Beck [Beck, 2000, p. 3] claims that the basic problem is risk, the underlying problem is that many projects are expected to make haste in the face of partial knowledge.
One way of characterizing XP would be to say that it was created by developers to allow them to do what they want to do, while reassuring the organization that the project will deliver successfully.
Developers really fear schedule slips because they are high profile and are never forgotten by the organization.
The disease affecting projects is two headed: ignorance and haste.
Ignorance is difficult to treat because it is hard to admit to our own ignorance.
Haste is an endemic problem in the software industry.
Unfortunately, haste makes the effects of ignorance even worse.
XP addresses these underlying problems by enabling developers to take the time to learn what they need to know while reassuring the organization about the eventual success of the project through predictable, sustained, and sustainable delivery.