Author Archives: Dimitar Karaivanov

About Dimitar Karaivanov

CEO and co-founder @KanbanizeInc., Speaker, Author, Lean Thinker, Portfolio Kanban enthusiast, passionate about efficiency at scale and hard rock.

Crossing the Kanbasm

Crossing the Kanbasm

Once in a while, people embarrass themselves publicly. As much as I hate these events, I’m no exception. One such mini-embarrassment for me was when I asked the following question on Twitter: Although I had the best of intentions, looking at the replies made it clear that I had something to learn. My attitude was […]

The Economic Problem with Queues in Product Development

The Economic Problem with Queues in Product Development

Reading Don Reinertsen’s book “The Principles of Product Development Flow: Second Generation Lean Product Development” was a truly enlightening experience, especially when it comes to understanding queues and the problems that queues cause in a regular product development process. Having almost five years of development behind Kanbanize, and many more before that, we came to […]

Kanban Charts Part V: Created vs. Finished

Kanban Charts Part V: Created vs. Finished Tasks

This article is going to explain a basic concept – how demand and throughput live together. It is going to touch a little bit from queuing and suggest ways to control both variables. As usual, we will be working with simple examples that make it easy to understand and apply the techniques that Kanbanize was built to enable. This time you will be an artist who owns an online business that doesn’t do so well, even though you send tons of paintings. Go through the entire post to figure out how you got out of this situation.

Kanbanizing the Waterfall

Kanbanizing the Waterfall

The traditional waterfall approach to building software (and other things) has been anathematized as being the worst thing that can happen to a company and has practically been banned from the industry for good. Its successor – agile has been discovered and promoted as the only way to do things properly. Is this applicable to everyone?