Keeping the backlog ordered

As a product owner I struggle with people adding bugs or other work in the backlog. This changes the backlog and I am forced to constantly check the ordering of the whole backlog as I am not sure of its state anymore. Any ideas on how I can improve on this?

1 answer

1 accepted

What we did is add two steps before our workflow - In review by PO and Low priority. Then we set up two boards for our project, a Kanban board that only showed the first two steps and a normal scrum board for the 'regular' workflow. This allows you to review items before they show up in the backlog, and to keep things in a low priority zone for later work.


By doing this you ensure that only reviewed items that are ready to be picked up by your scrum teams appear on the backlog.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,120 views 13 19
Join discussion

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot