Master features (also called epics) provide a layer of data between features and initiatives. They help you plan and manage work by containing multiple features that provide value as a group. You can use master features to prioritize and keep track of themes or groups of enhancements.
A master feature resides within the release in which it will be completed. The features that belong to the master feature can span multiple releases. You can, however, use them across multiple releases or products, as explained below.
Using the master feature across multiple releases
If you want to use a master feature across multiple releases, here are a couple of options:
- Place the master feature in the release you think it might be completed. And as the work progresses, you can move it to the next release if it is taking longer than expected. Moving features and master features to a different release is pretty common practice in Agile development.
- Create a new release that is focused on the master feature itself and make sure that the release is NOT time bound. Because you do not necessarily need to know when it will be complete, you can use the release to organize all of the other activities that need to be done when the master feature is completed.
Using a master feature across multiple products
A master feature that spans multiple products can only live in one product, where it will be owned and tracked. You can, however, link it to the child features in as many other products and releases as you wish.