Product backlog vs sprint backlog

I have a very small team, 3-4 people, and we're using JIRA and Confluence. We're on the road to using SCRUM with the sprint backlog and are trying to keep it groomed. The problem is the backlog fills with many feature requests, bugs improvements that simply won't be fixed in the near future or ever. Is there a difference between the product backlog and the spring backlog? 

My question is what recommendations are there to determine what goes in the backlog and where do the other items go for evaluation before they go on the backlog? I've created a page in Confluence called product requirements that was meant to be a place to hold new features for discussion. Where everyone can collaborate on each feature and modify it until it's mostly worked out. 

Any recommendations would be helpful.

2 answers

Hi Sean,

Everything goes in the backlog. Periodically you prioritize it and before each sprint begins you add the stories which you plan to implement/work on during the sprint in the sprint backlog and start the sprint.

Regards,

Peter

Consider using a separate project (kanban) for managing product backlog

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,712 views 17 21
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you