During the conversations with stakeholders, the team identifies and captures
what makes each user story complete, such as these examples:
- Unexpected behaviors
- Exceptions and error conditions
- Different types of users that might exist
- Data that needs to be in place
These conditions, also called story confirmations, help the team create
test cases to be conducted so that they can later evaluate whether the
user story is complete and accepted by stakeholders.
Detailing user stories does not imply that all user stories will
be detailed before commencing implementation on them. The level of detail captured
will vary, depending upon the needs of the project and the complexity of the
user story.
Nonfunctional requirements (such as expected performance, availability, adherence
to standards), as well as business rules that apply to a specific user
story, are also captured as story confirmations for that user story.
|