Product backlog with Scrum boards

[Tom Castonzo]

We have a JIRA Agile (epic) project that uses a scrum board. I see where to put the user stories, which is essentially the sprint backlog. Where or how is the product backlog entered and managed on the JIRA agile scrum board?

Thanks

[Nic Brough -Adaptavist- · Accepted solution]

Same place - product and sprint backlogs are analogous really.  (Think of it this way - what's the difference between a story for a product that needs some attention, and a story that should go into a sprint at some point?)

[Tom Castonzo]

I don't see them as analogous because the product backlog is supposed to be the running list of features, prioritized by the product manager and the sprint backlog is a slice of the product backlog that is being actively developed in the sprint. To me, those lists need to be managed separately

[Nic Brough -Adaptavist-]

But the items themselves are the same thing. The difference you describe is just the difference between "currently planned in a sprint" and "not planned into a sprint". Which you can see on the backlog view - sprints at the top of the list with the planned items in them, unplanned backlog below. I don't see any benefit from separating them. In fact, it's worse, because if you're looking at "unplanned", you can't see the stuff that is planned, and that can be useful when you're planning.

[Tom Castonzo]

I understand that product backlog and sprint backlog are the same item; my question is how to differentiate the 2 sp the team knows what to work on in the sprint. So where are sprints defined and tracked  if the user stories are the product backlog?

[Nic Brough -Adaptavist-]

Go to the backlog, and create a sprint. Move items into it by dragging them over the sprint line (or if they're mostly all at the top already, drag the sprint line down until it includes them). You can create multiple sprints there and drop things into them, handy for the cases where you look at something and go "not going to happen this sprint, but we know we need to do it soon". Once you're happy with what you have planned into the sprint, click start sprint. You'll still see stuff on the planning board, and your team knows what to work on simply by looking at the work view of the board.

[Tom Castonzo]

Ok thank you, that works for me