Scrum or Kanban: Which one to use?

Depending on the maturity of a product, different frameworks are helpful.

Scrum is widely used in the software development world. So is Kanban. Both frameworks provide benefits, both have avid supporters, but which one is best?

In my experience, one indicator of the better framework is the maturity of a product.

Young products: I recommend Kanban

Young products with a high degree of uncertainty and change can be better managed with a lightweight process such as Kanban. Everybody is learning as they go, people change the product's course comparatively often, and uncertainty may be so high that estimation is nearly impossible.

Mature products: I recommend Scrum

On the other hand, a mature and stable product reaps the benefits of Scrum. Estimation is easier, course changes are seldom, and sprints of two or three weeks can be finished without interruption. Planning into the future with a stable velocity is much easier with mature products.

Of course, you are free to choose whichever framework suits you best. I recommend beginning as mentioned above, then constantly evaluating if the choice is still right for the situation you are in.