The user story as described in the BABOK is information found that reflects and expands on the information in the context of agile development approaches.
User stories can be used to capture and prioritize user needs basis of
estimating and planning
product delivery generating
user acceptance test
way to monitor progress in delivering a value unit for tracing related requirements
basis of additional analysis unit of project management and reporting description
User stories are planning technique that enables agile teams to track features of value to customer or end user and are used as a basis for estimating work. User stories need to be
independent
negotiable
valuable
estimable
small and
testable
Following the basic invest criteria some of the elements included are the actual user story which captures The Who the what and the why
as an example as a user which is a role I need to do what so that what value can we deliver it also includes the acceptance criteria.
Acceptance criteria can be in Gherkin format. Gherkin format would be given when then.
