Think of the User Stories as an artifact that describes the work to be done, all from the customer’s point of view. This differs from the Product Requirements Docs (PRDs) of yesteryear, which focused more on what the software needed to do than on what the customer needed. The difference may seem subtle, but it’s important. In a well-functioning Agile team, the creation of the artifact and the discussion that produces it are focused more on the customer than they are on the software itself.
