Kanban Backlog

[Abhishek Gaur]

How to have the SAME backlog for a Sprint and Kanban boards (each having separate workflows)?

[Abhishek Gaur]

@Jack BrickeyCorrect! Only thing is the "Dev" in my case has 4 (not 3) verticals.

To Do > Design > Code Review > QA Backlog > QA > Done

....and QA has 3 verticals (as you stated)

Ready for QA (which was in the Backlog column) > In Test > Verified

The problem is, how to have two sprints with different number of columns (verticals) in the same board?

[Jack Brickey]

you cannot run two sprints off of a single board. see Nic's answer above.

[Nic Brough -Adaptavist-]

Make sure the two boards use the same filter.

You won't get quite the same backlog - Kanban doesn't have sprints to contain issues, but things outside sprints will appear the same.

[Abhishek Gaur]

Thank you for addressing that Nic.

Actually, we already have a backlog for Sprint (used by development).

Wanted to use the same backlog for Kanban (used by UAT team).

If Kanban board can't show the same backlog, then having another Sprint rather than Kanban for the UAT team is the ONLY available option?

At the end, we want to have a SAME backlog feeding two sprints with different workflows.

[Nic Brough -Adaptavist-]

A backlog is defined by the board filter and configuration.  It is part of the board.

If you have two boards, you have two backlogs, but if you use the same filters for both boards, they will be the same, drawing the same issues into it.

[Jack Brickey]

@Abhishek Gaur, just curious here; what is your end goal of having two different boards?

[Abhishek Gaur]

@Jack Brickey Glad that you asked that. Our project has two teams:

• Development+QA
• UAT

While the Development has a more elaborate workflow (To Do > Design > In-Progress > Code Review > QA Backlog > QA > Done)

UAT however has a relatively more straight forward workflow (To Do > Approved > Reject > Close)

Couldn't create two sprints (with different workflow) on a single board. Therefore, I am thinking of creating two boards.

[Jack Brickey]

Got it! I have done something similar though in the end I never really was thrilled w/ what i created. It felt to heavy and un-agile for sure. Ultimately, I think a single Kanban would have worked out better. Regardless it went something like this:

Dev - To Do, In Progress, Ready for QA with the last status being in the Done column

QA - Ready for QA (which was in the Backlog column), In Test, Verified