At my company we use Epics to categorise what I see as components of the system - various apps or islands of functionality.
IMHO Epic defines an effort that have a clear start and an end. To develop a web app is an Epic but to maintain it is a task on a given component.
I would like to propose to start using components but obviously there will be a resistance to change in the name of "we always did it this way". Are there any advantages of categorising things correctly? Is there something I can not do with epics that I could do with components? Maybe it's not worth the effort at all.
well with components you can have a lead and if a specific ticket has that component that lead can be assigned that ticket automatically. This helps triage tickets better. I dont know if that would be helpful to you. We use epics in a non agile way and just use them to keep track of certain projects with and without an end date. It just makes it easier to show management.
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs