I did Kanban for a few years. The process was something like this: 1. (bi)weekly review of backlog items for prioritization 2. When a dev is free, they pick a

I did Kanban for a few years. The process was something like this: 1. (bi)weekly review of backlog items for prioritization 2. When a dev is free, they pick a story from the board, and work on that exclusively (more or less) until it's done. 3. When a task is done it goes over to the QA area 4. QA grabs tasks that are ready for testing. They do the testing and then approve for deployment 5. Dev picks up a new story. We pushed to production pretty regularly as soon as features were done. It is nice to not have this idea of "end of sprint" and having your task done by then. You just work, push to test, and pick up something else.