“My team is using Kanban board but they seem to prefer to collate a couple of tickets then ‘do a release’ as appose to releasing each ticket. i.e. they move tickets through the workflow and then put them in a waiting column for days on end and then they do sporadic releases.
Recently, there was an interesting problem posed on a project management discussion board. The questioner asked –
“I have recently joined a company and to one of the projects that I’m engaged we have this Scrum team that has a mixed backlog (USs and Bugs).
In a recent post on a technical forum, a Dev manager had the question (paraphrased here) – My organization wants to operate in a Kanban way but maintain the structure of sprints and burn down charts to keep track of progress. Is it ok to do? Is Scrumban the correct methodology? If so, what is the best way to implement it?
It has been abundantly clear that in the last 3-4 years, the world of Agile has gradually come to be occupied by Kanban. While there has been a fair bit of the religious battle about Scrum vs. Kanban – which, while doing injustice to both Scrum and Kanban, has certainly helped to keep Kanban under the spotlight – the fact is that most consultants, coaches, and practitioners have been far more pragmatic and sanguine about it.
Try SwiftKanban Enterprise Plan FREE for 30 days.