 Let's begin with a simple question:
What is XP? As you will see,
it is a deliberate and disciplined approach to software development.
Next we might wonder when
to use XP. Risky projects with dynamic requirements are perfect for XP. These projects will experience greater
success and developer productivity.
But do we need yet another
software methodology? Actually we do. XP is a refreshing new approach. XP is successful because it emphasizes
customer involvement and promotes team work.
So how could this possibly
work? The most surprising aspect of XP is its simple rules and practices. They seem awkward
and perhaps even naive at first, but soon become a welcome change. Customers enjoy being partners in the software
process and developers actively contribute regardless of experience level. |
The rules and practices must
support each other. The XP Map shows how they work together to form a development
methodology. Unproductive activities have been trimmed to reduce costs and frustration.
I want to try XP how
do I start? Add a little to your current methodology or try it all at once. There is much here of benefit to
any project. What have other projects already learned
about XP? Some important lessons learned.
Where can I get
more information? There are classes,
conferences, books, and web sites.
Continue
the guided tour of XP by follow the trail of little buttons,
starting here. |
