Define requirements with stories, written on cards
Customers have the right to get the most possible value out of every programming moment, by asking for small atomic bits of functionality. Programmers have the right to know what is needed. These two rights come together in the user story.
Each user story is a short description of the behavior of the system, from the point of view of the user of the system. In XP, the system is specified entirely through stories.
Analysis can be loosely described as the process of finding out what the customer wants. Analysis can be done very formally, with objects and diagrams, or it ...