Handling a Project with a combination of Scrum and Kanban boards

Vj_m758ri

Hi,

I have a scenario where part of the stories follow Sprint Cycles and the rest of the stories fit Kanban mode of execution. So, I have created both Scrum board and Kanban boards. I have enabled Epics, Stories, Bugs, Tasks and Sub-Tasks. I have separate the stories in the fashion that if a specific Epic is the parent, the story should appear on Kanban board, otherwise on the Scrum board. While this works well for the Stories, I am looking for some support to understand how we manage Bugs, Tasks and Sub-Tasks to keep appearing on the Kanban board. Can I handle this through JQL or any automation?

Jack Brickey

Hi @Vj ,

there are a number of approaches here. The Key concept understand is that boards are defined by filters. These filters are created using various issue field attributes. So if you want to containerize project activities so that you can manage them differently, such as kanban and scrum, then we need to leverage some field within the issue. One method of doing this, which might work well here, is to use the Components field. Other possible solutions include: labels, custom field, or issue types.

As an example, let's say you decide to use components and these components  break down as follows:

• platform, backend, UI >> Scrum
• operations, PM, sales >> Kanban

then you would create boards from filters like this:

• scrum - project = abc and components in (platform, backend, UI)
• kanban - project = abc and components in (operations, PM, sales)

finally, one thing about components that I don't like in this specific situation is that you can have multiple components for a specific issue or none at all. What this means is that you can end up with a mix of components that would cross your boards resulting in the issue appearing on both boards. Also, if the components field is empty, where does it go? That would need to be defined. as an alternative, consider a custom field that is required at the time the issue was created. This custom field would be a single-select drop-down, and the user would have to select a single value.