Is there an actual Sprint Backlog as opposed to a Product Backlog or Backlog

This question is in reference to Atlassian Documentation: Sprint Backlog

Ask your question here...

3 answers

This widget could not be displayed.
Tarun Sapra Community Champion Aug 31, 2016

Both the terms "Sprint Backlog" and "Product Backlog" can be used interchangeably because generally teams follow Scrum methodology for product development and in Scrum you have work based on Sprints thus the Sprint Backlog is can also be called Product Backlog but vice-versa is not always true. As Product Backlog can be for next 3 months but only few features from that backlog will make it into the Current Sprint and some other top requested features of the product backlog which are highest in priority can be called Sprint Backlog as they will be worked upon in next Sprint. 

In JIRA there is just "Backlog" term and as I have explained above the Backlog items are used as Product backlog / Sprint Backlog.

This widget could not be displayed.

Agree with Tarun, but let's take it a bit further...

Assuming you have groomed the "Backlog" view in JIRA and assigned 10 issues to the current sprint. Now as you look at the Sprint view of the board, some issues are being worked on some are waiting to be worked on (i.e. To Do). I assume you are referring to those issues not yet being worked on as "Sprint Backlog". So... for most of us, the Sprint Backlog is the 1st column of the sprint board where we see issues that are part of the Sprint but not yet started. Hope this helps, ask some more questions if you need further help.

This widget could not be displayed.

Thanks guys for your response.

And you are right  in terms of the To Do column. That can be renamed as 'Sprint backlog'. However it would be useful if you could have a distinct backlog that is the 'Sprint backlog'. I say this as you can have items in a Sprint backlog that could cover 1,2,3 or 4 sprints.

But I think a renaming of that column is the best bet.

 

 

"you can have items in a Sprint backlog that could cover 1,2,3 or 4 sprints."

Well, according to theory (which by the way never keeps me from doing what works) you should not have stories/issues that go across sprints. (EPICs - yes, of course) If you have a lot of that happening, you might want to consider breaking things into smaller work items and/or consider that you are over committing the amount of work that can be done in a Sprint.

You might also consider adding swim lanes to sort things out. For example we have one for EPICs for the very reason that they tend to cross multiple sprints. We normally don't want to see them on a day-to-day basis so using a swim lane allows us to contract them.

Just thinking...

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Published yesterday in Marketplace Apps

The 7 hacks of highly successful automation

...there's anything I've learnt from working, it's that people are lazy! No offense to anyone reading this, but it's true and we can all admit it. The easier you make something for someone, the more...

113 views 0 9
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