How do you split epics into user stories?
- Data Boundaries: Divide the epic into separate bits of functionality along data lines.
- Operational Boundaries: Reduce the epic to its minimum viable feature, then build it out with additional slices of functionality.
Similarly, how do you split a user story?
- Split by capabilities offered. This is the most obvious way to split a large feature.
- Split by user roles.
- Split by user personas.
- Split by target device.
- The first story.
- Zero/one/many to the rescue.
- The first story—revised.
- The second story.
One may also ask, what are user stories and epics? Stories, also called “user stories,” are short requirements or requests written from the perspective of an end user. Epics are large bodies of work that can be broken down into a number of smaller tasks (called stories). Initiatives are collections of epics that drive toward a common goal.
Likewise, people ask, how do you split a user story in Rally?
When you open the Story that you want to split, click the "gear" icon at the top right of the Story and select Split. The UI that takes you through the splitting hasn't changed all that much, so you'll be fine there.
Should user stories be detailed?
A user story should be written with the minimum amount of detail necessary to fully encapsulate the value that the feature is meant to deliver. Any specifications that have arisen out of conversations with the business thus far can be recorded as part of the acceptance criteria.