Stories with backend and front end in different sprints?

[Sander Rietbergen]

I've found that the 'stories with backend and front end work' subject is widely asked and talked about in this community. The one thing I didn't find an answer on is the following:

I understand the scrum best practice of trying to plan the backend and front end work in the same sprint with a single story and then break it down in subtasks for backend and front end.

But sometimes it happens in our project that we know on forehand that the backend and front end work on a story can't be planned in the same sprint due to several reasons. What would be the best practice in this specific situation? What we do now is create separate Story tickets for backend en front end so it can be placed in different sprints but I think this isn't the way scrum sees it as best way to do it.

[Stephen_Lugton · Accepted solution]

@Sander Rietbergen you'll get different answers to this, but the best thing is to do what works.

Scrum is a framework to help deliver business value, and you'll find that 'best practices' have developed around that, but they aren't the only practices.

Your approach of having separate tickets for backend and frontend work delivers business value, so if you can't do both in one sprint there is nothing wrong with doing them in separate sprints.