User stories capture the intended functionality of the system under development, from the user role
perspective. They are simple, clear, brief descriptions written using business language in the context in
which the need or capability will be used in the system.
A user story is in fact a reminder for further conversation between the team and stakeholders. User stories are
written down, but they are not meant to be contractual, or even interpreted without further discussions with the
stakeholders. The on-going interaction between stakeholders and the team (to discuss the details of a user story) are
more important than the resulting textual description itself.
|