Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,294,619
Community Members
 
Community Events
165
Community Groups

Can a User Story be worked on in two different sprints?

Hello,

I have a question about how to successfully set up User Stories to be worked on two different Sprints. At my company, we run two different sprints - front-end (which is always one sprint behind) team and a back-end team.  (The purpose of that is that f-e would not need to wait on b-e to finish their part). 

The product team writes Acceptance Criteria on the User Stories. Teams aim to work on the same User Stories, just create different sub-tasks, e.g., back-end team creates sub-tasks for their sprint, same with front-end. 

I have never worked in this way, that same US would work for different Sprints, teams would be able to close sprints with sub-tasks, they would have a burn-down chart, and everything would work smoothly. 

 

Has anyone faced a similar situation? Any tips on how to set it up for success?

The main goal I would like to achieve is a visibility of the Parent-child relationship and being able to provide transparency for the Product team about the status of User Story, despite which Sprint US is in. Any help? :)

Thanks,
Donata

1 answer

1 accepted

0 votes
Answer accepted
Benjamin Community Leader May 11, 2020

hi @Donata -

I have work a few options before.  Feel free to choose what would work best for you:

1. Back end and Front End is on the same team. Backend works in SP1 for SP2 Front end work. Front End works in SP1 to works on what may be available at the time to do. Therefore the story will be spread across 2 sprints but backend-end sub-task are completed, so less to do in the next sprint. 

2. The story becomes an Epic where stories are associated to the Epic. One story for back end and one story for front end. Product Team can use the Epic panel to see how all the related stories are doing in that epic. Plus the burn chart will work much better instead of each not being able to ever burn down. 

 

3. Back end and front end work in smaller chunks where they can deliver in one sprint. Doesn't look like its possible in your case base.

Hope this helps.

Hi Benjamin,

 

Thank you for your answer. That helps. 

How manage the story points in the first case? This doubt is about the metrics and dashboards of closed sprints considering that the front end will estimate story points in a different planning meeting.

1. Back end and Front End is on the same team. Backend works in SP1 for SP2 Front end work. Front End works in SP1 to works on what may be available at the time to do. Therefore the story will be spread across 2 sprints but backend-end sub-task are completed, so less to do in the next sprint. 

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Software

Upcoming changes to epic fields in company-managed projects

👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...

14,226 views 35 44
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you