Does your team use Epic, Story and Feature ticket types in the same project?

We have Epics for larger features.

I want to replace Feature with Stories, but product team wants to keep Features as a high level request with use cases.

Wondering how your teams work with these 3 issue types and if one just gets cloned or promoted when needed.

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes

I think if you ask 10 different companies, you'll probably get 10 different answers. :)

However, the generally accepted idea (supported by the Scaled Agile Framework SAFe) is a hierarchy where many stories form part of one feature and many features form part of one epic. Essentially it is a size description.

Have a discussion with the product team, try to understand why they want it like that and let them know why you want it changed, but in the end it doesn't make a huge difference