By now — over a decade since the Kanban method’s introduction to knowledge work — most people have at least heard about it, if not tried it. If you’re considering adopting Kanban for your team, here are a few tips on making it a success. Kanban is a way of…

Having worked on the kanbantool.com service for over a decade, it’s rather difficult for our team to imagine people not using some form of a workflow management system. But a recent trip to fellow business offices made us think about such individuals, as well as teams. …

What’s an epic? In Agile workflow management, the term epic can hold different meanings for various people and teams. Some see an epic as a general outline or sketch of a task. For others, it’s a goal that breaks down into a series of small jobs. There will also be those people for…

One of Kanban’s biggest strengths and a core reason why teams choose to use it is its ability to manage change. The change in your process, in your team’s goals and mindset. It helps to deal with change by keeping the process stable, sustainable, and service-oriented. …

Agile work environments and processes center around self-organization and adaptation to fluctuating demands. Therefore a leader of an Agile project, or an Agile company department, should have the ability to let people make their own decisions and make them fast — right? Sometimes that can seem like the opposite of…

Would you consider it a conceptual travesty to use the Kanban Tool to manage a Scrum-based process flow? Well, our customers don’t! Kanban Tool boards are widely open to personalization and can map out either of the frameworks with ease. Kanban vs. Scrum, in short A Scrum process: bases on short iterations — Sprits, typically…

One of the core ideas put forward by the Agile Manifesto was for teams to welcome changing requirements from the customer, also when they’re already well into the project’s development. Arguably, it’s one of the ways Agile gives teams a competitive advantage. …

When working as a team, it can be challenging to arrive at a shared conclusion and an agreeable result, to put it mildly. And, where teams working on the more technical aspects can rely on a binary classification of the issue — something is either done right, or it’s not…

A typical storyline behind teams wanting to start using Kanban is that they received an incentive from the management to “get more Agile”. And, let’s be honest, this is not at all a bad reason to start! …