Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Work spread over multiple sprints

Apoorv Bhargava
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 18, 2022

I have setup following hierarchy in JIRA, user-story (issue) > BE subtask & FE subtask. Since we have a small team FE tasks are completed and queued up while BE tasks follow later. This is leading to piling up of user stories on sprint board. What would be the best approach to keep track of the issues and keep the sprint board clean?

 

FYI - reason to use the above hierarchy is to keep track of completion of each user story.

 

Looking forward to hear your suggestions.

 

Thanks,

Apoorv

1 answer

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 18, 2022

Welcome to the Atlassian Community!

In Scrum, you should be sizing your stories such that they can be executed (ideally many of them) within a single sprint.  "Work spread over multiple sprints" should be a rare exception.

Your best approach is to refine your stories better, breaking them up into more manageable stories.  Or you could increase the length of your sprints so you can fit them in.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events