Currently we are using epic as a large container for product feature-holding stories.
Examples of some of my Epics: Feature 1 , Feature 2. It is never ending and explains the product structure. Though we are not able to use it very effectively.
Same time we are using fix version for the projects - for example - Feature 1 has 10 stories but if we are working on its phase 1 and only 5 stories are going to be delivered then we mark all those five stories as part of fix version with name feature 1 phase 1.
Want to understand the best practices and easy-to-use method?
Option I am exploring is
Epic as project and having concrete end time.
Fix version as every release containing all the features that would release in that month
Hi @Sanchit Korgaonkar
It's Mary from Planyway for Jira: workload, roadmapping, time tracking
Here are some best practices and considerations based on your current situation and the option you're exploring:
Using epics as large containers for product features is a standard practice. However, treating epics as projects with concrete end times can help in a few ways:
Leveraging fix versions to represent releases is a great way to track what features and stories are going out in each release cycle.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.