Two teams: one Kanban board and one Scrum board

Question

Hello,

I am working with two teams in a project, a kanban team (operation) team and a scrum team (with 2 week sprints). Before, the both of the teams were scrum teams and had sprints. We have used a roadmap until now but unfortunately the kanban teams epics and issues are not shown in the roadmap anymore, since the roadmap places out the issues based on sprints. Can I somehow make the kanban teams issues showable in the roadmap so that we can see when the issue has ben done?

One more question, now since we have one kanban team and one scrum team, we have two different boards and also two different backlogs. We are not happy with that since we want all the issues in one backlog but two different boards, how can I fix this?

Is it possible to create on master backlog with everything visible in one backlog? We want a good overview.

Nic Brough -Adaptavist- · Answer

To create a common backlog, your teams will have to work on one board.

It's not immediately obvious from the docs and tutorials, but a backlog is not an independent thing - it is part of a board.  The backlog is best thought of as a "feed" for a board - it's the issues that are candidates to end up on your board.

If you have many boards, each one can have its own backlog, there's no such thing as a "common backlog"

Alma Agic · Answer

Thank you for your reply.

But I am still a bit confused. How can I create one common backlog for my project? It should be possible to have several boards (kanban and scrum) but still one common backlog.

Nic Brough -Adaptavist- · Answer

Welcome to the Atlassian Community!

This is not going to work.

You have probably done the right thing by having one board per team, that's how it is intended to be used.

But that means two separate backlogs.

You can, of course, have issues that appear on both boards, but that can be horribly confusing for your teams - it becomes very easy for a team to pick up an issue for the other team.

And you can't add Kanban items to Sprint roadmaps.  They don't do sprints.  Kanban is not supposed to be plan-able, it's "drinking from the firehose", not "taking a drink when you know you are going to need to".

Unless you start doing release planning for the Kanban issues (grouping them into Epics for release later), and you'll then be able to see them in the release section of your roadmap.