[matwood]

> We no longer have drawn out sprint planning meetings where we discuss requirements of features that we never end up working on in that sprint. We don’t waste time debating complexity of features. Everything is now just ad hoc.

I'm curious about a few things, if you don't mind answering.

When do tickets get broken down into manageable chunks? Who does the breakdown?

When is a rough cut of effort put on a ticket? S/M/L often matters when making priority decisions.

[oomkiller]

A breakdown step in your development process breaks down work into equally sized chunks, that all count against WIP limits. If you're interested in using Kanban for software development I suggest checking out Eric Brechner's book and youtube videos.