What Does a User Story Include?
User stories should be independent and stand on their own. Each user story describes a bite-sized feature that is distinct from other system behaviors. One large feature can have several different user stories. Each part that can accomplish a goal should have its own user story to mark it distinct from other parts of the feature.
Developers often have to write code for individual parts of a feature. It is better to have user stories for each of the individual pieces so that developers do not have to write an entire large feature in one sprint.
Unlike traditional development, user stories of Agile are negotiable. Most functional specifications in waterfall development are set in stone. Once an organization clears a spec, the product must match that spec to the letter.
Changes often require several official documents and stepping through layers of red tape. With Scrum, user stories remain negotiable even until development is finished. If a user story is deemed unnecessary, it can be scrapped or reworked into something more useful. Some user stories may describe larger features that would be difficult for developers to complete in a single sprint. In these cases, the team may split the user story into multiple smaller user stories.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: