Breaking down the first user story in this section will shed light on more specific functionalities that the feature can have. It is possible that the team can further break down the user stories however they like.
Some questions that can be asked to know when a story can be split would be the following:
1. Does the story seem to be too complex for estimation?
2. Can this be finished with a Sprint?
3. What are the dependencies of this story?
4. Is there anything that is unclear in a technical or business manner?
Finding answers to questions like these can help the team decide whether the user story is actually big enough to be an epic and can be split into more user stories.
Epics are large stories that can span sprints and are made up of smaller user stories. They are placeholders for the work to be done and group functionalities by specific user work-flows. Product backlog management can be improved by working with the stakeholders on their feedback and discussing within the team on deciding how to construct epics and user stories.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: