The AgileBlog for Kanban

The Psychology of an Agile Mindset

Job postings for Scrum Masters, Agile Coaches or Agile Leaders all have one requirement in common. It is always part of the job to train and support an agile mindset in the team, the organization or the company. But what does it actually mean to have an agile mindset, and why is it so difficult to establish an agile mindset at all?

Is There a Planning Meeting in Kanban?

Is There a Planning Meeting in Kanban?

Is there a planning meeting in Kanban? While development teams often think, that using a task board and doing Kanban are the same, that’s not true. Kanban is a system which is highly focused on core metrics, and of course work and delivery is planned in Kanban organizations. This article explains how work can be planned and organized with Kanban cadences.

Where to Find Your Next Task in a Pull System

Where to Find Your Next Task in a Pull System

Where to find your next task in a pull system? Though, the answer to this question seems simple at first glance, human beings often times tend to choose the task with the biggest fun factor. This article shows why it makes sense to select the task according to specific criteria.

A Beginners Guide to Story Mapping

A Beginners Guide to Story Mapping

A beginner’s guide to story mapping answers the questions many organizations ask about agile transitions. Where do our requirements come from? How should our teams be structured? In what form do we deliver our product and what value does it deliver to the customer? Story mapping can provide answers to all of these questions.

Technical Debt is not a bug

Technical Debt is not a bug

Many authors consider technical debt and bugs identical and equate the reduction of bugs with the repayment of technical debt. Unfortunately, this is wrong. This article explains the characteristics of technical debt and bugs, and why it is important to differentiate.

Increasing Transparency With Technical Stories

Increasing Transparency With Technical Stories

Agile purists often believe that there are exactly two types of requirements in an agile organization – epics and user stories. In this article I explain why it makes sense to look at technical stories in addition to user stories.