Hello everyone
I am new to agile development, and I am using VSTS.
I have two questions regarding work items.
is it possible to have an epic under an epic( Epic --> Epic)?
and is it possible to have an an epic under a feature that is under another epic (Epic --> Feature --> Epic)?
Can you please provide me with examples to make things more clear to me ???
Thank you in advance
Community moderators have prevented the ability to post new answers.
Dear yasmeen,
I am afraid not; A sub-epic in that sense is a "story". You could add the Portfolio addon and use "initiatives" to group together Epics though - a layer above Epic rather than below.
Or.. you could just add sub-tasks to the Epic.. but not an epic under an epic.
Friendly Regards,
Jeremy Mooiman
Jeremy,
Thanks for answering me.
So I can understand that there is no case that we can have one epic under another epic, nor a hierarchy of an epic- feature- epic?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Yasmeen,
Correct, this is by design made that way. The ''Epic'' is always the highest point in the hierarchy. You could try creating a structure based on Issue Links and Automation.. or just with stories / sub tasks.. but a true Epic inside an Epic without tinkering is not possible and goes against the agile way of working.
Friendly Regards,
Jeremy Mooiman
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Yasmeen,
Agile would recommend a simple structure of Epics, Stories and "Subtypes" (Tasks or equivalent). If you open your perspective to SAFe, that could lead to Initiative -> Feature -> Epic -> Story -> Subtypes, this can be supported in Jira using Jira Portfolio and would be transparent at a board level.
In order to answer your question I'd recommend going that way if you need more than 3 levels of hierarchy which is the Jira standard (and Agile). Always keep in mind that Atlassian tools are meant to improve your team's experience and complexifying process with unnecessary levels is never a good idea, that being said if you need 5 levels, above is an idea :)
Hope this helps
Cheers!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Apply agile practices
Transform how you manage your work with agile practices, including kanban and scrum frameworks.
Learning Path
Configure agile boards for Jira projects
Learn how to create and configure agile Jira boards so you can plan, prioritize, and estimate upcoming work.
Jira Essentials with Agile Mindset
Suitable for beginners, this live instructor-led full-day course will set up your whole team to understand how to use Jira with an agile methodology.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.