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.
Sometimes we need to let others know that we have an issue and we need help. Kanbanize makes it easy to visualize this and measures everything behind the scenes. Learn more about the next step towards perfection in the article about Block Resolutoin Time.
With the task distribution chart you can track the number of tasks on your Kanban board, how much time has been spent on different types of work, how your work is distributed by person and many more.
So, what is it that makes a Kanban implementation successful? There is not a definitive answer to that question, but I will attempt to “prescribe” my own rules that have helped us so far.
The cycle time chart is your best friend in your endeavor to conquer the world of Kanban productivity. If you want to know more about this metric and how to read the chart, go through the entire article and share your feedback.
Cumulative flow is one of the most powerful tools available in the lean world, and it is a pity that many people fail to read this graph correctly. If you feel you need more understanding about this Kanban chart, please go through the article and check our simple explanation.
This article is part of a series that will address what kind of KPIs a SaaS company needs to track to make sure all parts of the business are doing fine. The focus of the current post is on software development or the so called RnD department of the company. The article is intended primarily for development managers, project managers, team leads or other senior staff, but anyone who’s interested may check what we have to say. Let’s get rolling without further introductions.
As Agile is outgrowing IT and the world starts talking about Business Agility, we see Scrum attempted in various setups – Marketing, Sales, Legal, Management. Although it can be technically used in such contexts, Scrum was invented to help software teams deliver software and as such, it dominated the industry. But the most recent State […]
Many Kanbanize users are software guys that have been practicing SCRUM for a while and for some reason (which we all understand very well) want to move to Kanban. Ex-scrummers, you’re on the right track to be looking for something new. For more details how to do things better, check the article itself.
Being fond of the Kanban culture pushed me to experimenting. I’ve tried pretty much every technique that I could think of (with varying success) and that is how I’ve experienced not only the bright side of things, but also its dark one. In this post I would like to share three of the greatest challenges that I’ve had along the way and probably keep you far from the dark side, my dear padawans!