Approval and Prioritisation
After the stakeholders have given input, the Scrum team begins to put together user stories for approval. This includes a number of different steps to create the most useful and direct user stories. The Scrum team must examine whether something counts as a full user story or just a trivial action. Many small actions might need to be combined to be a single user story. On the other hand, large stories in the form of epics may need to be broken down into several smaller user stories to cover individual features.
The product owner role is responsible for prioritizing the user stories. This prioritization gives developers notice of what they will be working on next. Through extensive research is wasteful this early in the development process, it does give developers a high-level overview. This gives them a better understanding of how and where each small piece will fit together and provide consideration for other development tasks.
Estimation
Once user stories have been approved and prioritized, they must be estimated. Where traditional development uses hour estimates, Agile development uses story points. These story points do not translate directly to time but give a general idea of effort. They are relative and indicate which user stories require more or less work than others.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: