agile > chapter 2 launch and planning > 9 splitting requirements

Splitting requirements

It is essential that we do not create epics when preparing user stories. An epic cannot be completed in a single iteration and this makes it harder to implement and manage if a change occurs at the end of the current iteration.

Epics are too generalized. This leads to the estimation of the work required to implement them too difficult. It also makes it difficult for us to determine if the work required to complete the user story is finished.

As a student, I want to be able to use the learning management system in order to achieve academic success.

The definition of "Done" for this epic is too difficult to define. It might even be outside of the scope of what is achievable by using the product.

When the scope is too large or too vague, we need to divide the requirement into smaller, more manageable ones.

How to split requirements

Best practices