"Fake" sprints are a nice way to organize different sections of a backlog, but that's not what they're intended for. Other than quick filters, are there any other tricks to organizing issues using the Kanban backlog if there are multiple sub-teams who need to work from the same backlog prioritization?
Here is one possible solution - multiple boards (we did something similar)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Swimlanes are for the "Active"(Kanban board) view and not for the backlog view.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Ollie Guan Thanks for the suggestion. Unfortunately, that's only for the board and we're only looking to group issues in the backlog.
@johndpatton Thanks for the link! We do use multiple boards, but need to pull from one backlog.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
One other thought was that you can have different fields on your backlog cards than your board...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Interesting idea! I'll have to add the new field and give it a try.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.