attitude that developers are responsible for proving to their customers
that the code works correctly, not customers proving the code is broken.
the project you will be getting intense feedback in many ways, at many
levels. Getting working software into
the customer's hands will drive
the project's iterations with a steady heartbeat and release of
software for money spent so far. Changes in requirements will be part
of that feedback and gladly accepted.
receive feedback constantly by working in pairs and testing code as it
is written. Managers get feedback on progress and obstacles at the
daily stand up meeting. Customers get feedback on progress with
acceptance test scores and demonstrations every iteration.
to follow the little XP logos at the bottom of the pages to
finish your quick guided tour or take some time to explore the