By Alex Yakyma.
We just finished the Business Epic page in Scaled Agile Framework recently and it has a bunch of useful approaches of how to split business epics into smaller items (sub-epics and features). Following are the key methods used. We split epics by...
- Product / Subsystem / Component
- Success Criteria (note that this is an analogue to user story acceptance criteria, however it stays at the higher level of abstraction and thus expresses business benefits rather than the requirements to the functionality. Hence the different name)
- Major Effort first
- Market Segment / Customer / Class of User
- Defer System Qualities
- Risk Reduction / Opportunity Enablement
- Use Case Scenarios
Prior to that we published the Architecture Epic page which also has interesting considerations in terms of splitting and incremental implementation of large technical initiatives.