nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

scrum backlog view without board?

Calvin Hoot

I understand that a board drives the UI for an agile project. Is there a way to add a backlog page/view (like in Scrum templates) without having to switch to a separate board?

WHY: I created a project with a kanban template but would like to drag items between either an 'icebox' that's off the board into the backlog, or move backlog off the board and drag them into a 'ready to pull' status. This way the board is manageable but still gives a way to quickly prioritize.

Accepted answers

Nic Brough -Adaptavist-

You don't have to switch to another board. Just create a new Scrum board and change the filter to be the same as the one for the Kanban board. People can work in either board and jump between them if they want, it's all the same underlying data

Kanban doesn't have the concept of a backlog, so you won't quite get what you want.

Calvin Hoot

For anyone looking for an answer rather than an argument about Kanban, this is now a feature that can be administered within JIRA Software Labs:

Kanban Backlog.png

All comments

Nic Brough -Adaptavist-

Kanban doesn't have the concept of a backlog, so you won't quite get what you want.

Calvin Hoot

Kanban absolutely has the concept of a backlog whether it's called that or a pool of stories/issues/tickets, or has acceptance criteria, or whatever else is needed, there is some mechanism of managing ideas that aren't board ready.

Calvin Hoot

also, this won't explicitly work; for the work to show up on the scrum 'active sprints' a sprint has to be created to capture all of the kanban backlog. If we started to work from this new board after modifying the backlog, closing a sprint does not 'release' and the tickets themselves would show up as part of the kanban board should you switch back.

Nic Brough -Adaptavist-

Sorry, I phrased that incorrectly. Kanban's backlog is the first column on the board, it's not that it doesn't exist, it's just there so you can work on it. You're moving away from doing Kanban "properly", so it's not supporting you. Not that this is a bad thing, Kanban is often over-simplified for the real world. If you want a method of moving the backlog towards a more Scrum model where you don't put things in the to-do pile until they've passed some gate, then remove the first column from your main Kanban. Issues that aren't ready to go won't be on the board. Then come up with a way of managing them on to the board. Using a scrum board is one way to do it, but you could simply slap a "backlog" Kanban in place too. Let's say your current Kanban board has columns "new, approved, in dev, in test, done" which are identical to the status. Remove "new" from it. Create a new Kanban board with columns "new, approved, in-progress (which contains the in dev/in test status), done". You can manage your backlog in the second board

Calvin Hoot

For anyone looking for an answer rather than an argument about Kanban, this is now a feature that can be administered within JIRA Software Labs:

Kanban Backlog.png

Nic Brough -Adaptavist-

Bear in mind that it may go away, as it's a Lab experiment (it probably won't, but don't rely on it while it's a Lab)

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-software

kanban

scrum