How do you create a Kanban backlog? What is a good practice?

[Jim Lile]

I am working with a company that is beginning to use Kanban for integrations. They have defined a process and built columns and status to visible represent priorities. My question is, the business will want to keep planning with the PO and architects some complex Boomi integrations to prepare for 3rd party/offshore developers, is it best to define the work need in the EPIC or how can I simply use a standard backlog? Today I have just Roadmap and Kanban board and we feel it would make better sense to have a backlog of stories and major tasks we need to create. Why shouldn't we take this approach?  

[Jack Brickey · Accepted solution]

Hi Jim. I’m not exactly following you. I’m trying to understand what’s unique about your situation that would make you consider something other than simply using a backlog. Have you traditionally use backlogs in Kanban before and they work for you?

[Jim Lile]

I would like to simply use a backlog in a Kanban board, that is not standard in Jira but I'm seeing some configuration steps to make this possible. And to answer your questions "Have you traditionally use backlogs in Kanban before and they work for you?" Yes. I find there are times to add future detail, even if just as a reminder. 

[Jack Brickey]

Thanks Jim. So were you then successful to set up your backlog as desired?