Kanban and Scrum board in one project with different backlogs

[Zaal Gachechiladze]

Hello,

I want to do the following thing:

Want to create Kanban board for Discovery work, and when the Discovery phase is over and the issue will be in the Done column, I want the issue to appear on the Scrum boards backlog. 

This means I want them to have the separate backlogs. 

How can I do that?

[Carlos Garcia Navarro · Accepted solution]

Hi @Zaal Gachechiladze , you could do this:

1) Create a status called 'Discovery' and modify your workflow so this is the status assigned to tickets that were created (or maybe do this for a specific issue type)

2) Create a kanban board where the first column is called 'Discovery' and link it to this status. Have another column called 'Backlog' assigned to status 'Backlog'

3) Create a scrum board where the status backlog is assigned to the backlog view

 Issues that are created will show up in your kanban board first , but once they've been moved to the 'backlog' column in the kanban board they'll show up in the scrum board.

Would this help?

Carlos

[Carlos Garcia Navarro]

Including some pictures:

This is the workflow that shows new tickets being linked to the Discovery status:

 

This is the new Kanban board where I've created two columns, one for Discovery and one for Backlog (you can add more columns if your process is more complex):

This is the Scrum board where the status 'Backlog' is assigned to the 'To Do' column. 'Backlog' was also the status linked to the column 'Backlog' in the kanban board:

Hope it helps,

Carlos

[Zaal Gachechiladze]

Thank you! this was really helpful!

[Carlos Garcia Navarro]

I'm glad to hear that it was useful, @Zaal Gachechiladze :-)

If it addressed your question, please consider accepting the answer so it can help others in the Community who may also have a similar question. Thanks!

[Anshuman Borah]

While I see the manner how both Kanban  and Scrum can be accommodated within one Project. But there should be a driving principle or a logical reason behind each. While we do the Product Development and its releases through Scrum, we can essentially cover its 'Support' and future 'Recommendation/ Changes' through Kanban.

Also, worth mentioning if the Backlog Items have the common inception point, i.e. one Epic. That means, if we have 4 Stories under one Epic, then CAN -- The first two stories be on Scum and the remaining two be on Kanban. Which isnt correct!

So, would we agree that, a common pool of work items, i.e. the backlog can feed into two channels of Agile - Scrum and KB, provided they are distinctly separate from one another. Perhaps, YES!

But, in short, it could be really complicated to try to use both agile boards/methodologies on the same body of work, this approach is not something I would not suggest as a Product Owner. Although it is possible in Jira.

Better to have two projects to cover the two aspects of a Product Development & Management, always.

[MB]

@Carlos Garcia Navarro  Great post of a really good example on how to use both scrum and kanban for a project.  I thin I want to implement this process for my team.  Can you tell me if you created this project as a classic or Next gen?

[Zaal Gachechiladze]

hello,

I have a Discovery team with whom I work to create backlog for the Development team. They have certain flow of the discovery process and the Kaban flow is more convenient. When the PBI is ready to be moved to the Development backlog we put it in the last column of the Kanban board, which is Backlog and it is automatically visible in the Development backlog too. 

If I had two Development teams working on the same project I would use two scrum boards with shared backlog. Not this flow. 

[MB]

Hi @Zaal Gachechiladze Thank you for the clarification.  I actually have one small Development team that does the discovery and development.  Currently our backlog lives on a scrum board and many of our issues need proper discovery before moved to a sprint.  I am looking for an easy way to distinguish what needs or is currently in discovery from the backlog in anticipation of being moved into a sprint.  I think I will fiddle around with this idea a bit more, but I like your suggestions.

Many thanks,

M

[Carlos Garcia Navarro]

Hi @MB , just to answer your previous question, I used a classic project.

[MB]

Thanks @Carlos Garcia Navarro . I really like your solution for managing the backlog.