Product Backlog with Epics instead of User Stories is this a problem?

[Jacques.Bertrand]

I have a Client using Epics instead of User Stories to build and manage his Product Backlog (SAP Hana conversion). His Product backlog only feature Epics NO US. Epics have almost the same structure as User Stories i.e. They are described the same way: " <As a User>< xxxxx> etc..." It has acceptance criteria, DoD, DoR, priority. Epics are broken down in User Stories during Sprint Planning and are used along side their relevant tasks during Daily Scrums. Might I have your views about this unusual way of working and the potential risks that this might represent. Thanks.

[Nic Brough -Adaptavist- · Accepted solution]

Welcome to the Atlassian Community!

Actually, I don't think that's a problematic way to work.  Assuming the Epics are large overarching things that are unlikely to get done in a sprint, and you sprint on the stories that come out of them, there shouldn't be an issue.

The only headache I can see is that Epics are not sprint items, so I wouldn't be trying to use them in the sprint, but that's fine because you're creating the user stories that you would sprint on anyway.

[Jacques.Bertrand]

Thanks Nic, this is what I thought. I think that one obvious advantage of operating with Epics instead of User Stories at Product Backlog level is that the size of your Product backlog is kept relatively small and changes not that frequent as well.