How can we visualize backlog issues in one project for two boards

Question

We are setting up one Kanban board and one Sprint in one project that uses one workflow. The input is the backlog. The backlog for Kanban is new input, and for the sprint the issues that were finalized in Kanban.

The issues finalized in Kanban need to be in the backlog for the Sprint as there they will be selected to pick up in the current sprint. We cannot have all issues automatically being addressed "To do" in the Sprint and also do not want to see all Kanban issues in the Sprint backlog.

Bart van Leeuwen · Answer

It's another way to look at a process, but visualization makes it more clear what's happening. And when. We understand not only how we want to work, but also can explain why we do it this way. Which helps heaps in onboarding as well!

John Funk · Answer

Looks good - we have started using something similar for our upstream/ideation process (your left side) and downstream/execution (your right side)

Bart van Leeuwen · Answer

Thanks for drilling into this @John Funk as we have been working towards a newer version and started testing this solution.

We are testing with functionality of a second backlog like function. It all starts with creating in the Design Backlog, after the design is ready for being build we move these to the TO-Do phase where the Build team can pick these up and add them in their sprint when it's time. It looks like this: