Episode 28 Kanban Myth - Items don't move backwards

Introduction

In this section, the hosts introduce themselves and their drinks for the night. They also mention a myth about Kanban board design that they will be discussing.

• The hosts introduce themselves and their drinks for the night.

• They mention a myth about Kanban board design that they will be discussing.

Basics of Kanban Board Design

In this section, the hosts discuss the basics of Kanban board design and exit criteria.

Establishing Workflow

• The hosts reference a previous video where they talked about establishing workflow.

• Exit criteria is discussed as a list of criteria that need to be met before a card can exit that column.

Definition of Done

• Definition of done is mentioned as everything that happens at the end to make sure that something is done well.

Dispelling Myths About Kanban Board Design

In this section, the hosts dispel myths about Kanban board design, specifically regarding items moving backward on the board.

Moving Backward on the Board

• The myth that items cannot move backward on a Kanban board is introduced.

• The hosts confirm that it is possible for items to move backward on a Kanban board under specific conditions.

• Building a cumulative flow diagram correctly can accommodate items moving backward without affecting the line graph.

Definition of Done

In this section, the speakers discuss the concept of "Definition of Done" and how it applies to workflow stages. They provide examples of exit criteria for different stages in a workflow.

Importance of Exit Criteria

• The "Definition of Done" is an expression used in some parts of America that refers to the exit criteria for each stage in a workflow.

• The exit criteria for a stage must be met before an item can move forward to the next stage.

• The exit criteria can be met earlier on in the workflow, not just in the current column.

• Each column in a workflow should have two or three bullet points outlining its exit criteria.

Example Workflow Stages and Exit Criteria

• A coding column might have exit criteria such as code being written, reviewed, checked-in, passing unit tests, and having green CI.

• A testing column might have exit criteria such as all acceptance criteria being tested with integration tests, test cases being documented and passed, and demoing to a product representative.

• It's important to note that work from future columns can be done earlier on if it doesn't interfere with meeting the current column's exit criteria.

Importance of Exit Criteria

In this section, the speakers explain why understanding and adhering to exit criteria is crucial when discussing items flowing backward through a workflow.

Importance of Adhering to Exit Criteria

• If an item moves forward without meeting its current stage's exit criteria, it means it should never have exited that column.

• If an issue arises after an item has moved forward, it's important to go back and ensure that all exit criteria were met before the item can continue moving forward.

Moving Items Backward in Flow

In this section, the speaker distinguishes between moving an item backward in flow due to a mistake and moving it back because of a bug found during testing.

Moving Items Backward Due to Mistakes

• It is okay to move an item backward if it was mistakenly moved forward.

• This is usually done when an extra criteria was missed or the item was not ready to move forward.

Moving Items Backward Due to Bugs Found During Testing

• If a bug is found during testing, some people think that the item should be moved back to coding so that developers can fix it.

• However, this is not necessary if the item still meets all the exit criteria for the coding column.

• The point of having a test column is to find and fix bugs where they are found.

• Fixing problems where they are found will surface improvement conversations over time.

When Should Items Move Backward?

• If we violate our own policies, then items should move backward.

• For example, if an item has 28 acceptance criteria but only four were met during testing, then it should be moved back.

• However, if all 28 acceptance criteria were met but there's still a bug, then it doesn't need to move back.

Why Does the Myth Exist?

• The myth exists because people equate stages with people rather than what happens at each stage.

• People believe that items shouldn't move backward because of who works on them rather than what needs to happen at each stage.

Moving Items Backward on a Kanban Board is a Myth

In this section, the speakers discuss why moving items backward on a Kanban board is not as bad as it seems. They explain that while it's generally better to move items forward, sometimes mistakes happen and it's okay to correct them by moving items backward.

Why Moving Items Backward is Okay

• Accidentally pulling the wrong item forward in Jira can happen easily.

• It's reasonable to move an item backward and pull another one forward if necessary.

• Moving an item backward should be the last thing you consider unless it's completely obvious that you made a mistake.

• Correcting mistakes by moving stuff backwards is okay.

The Importance of Having Conversations

• It's important to have conversations about what allowed you to move something forward when it shouldn't have been moved forward.

• Have conversations about how to prevent future mistakes from happening.

Conclusion

• While people say not to move stuff backward, their heart is in the right place. Mistakes happen, and it's okay to correct them by moving things backward.

• Leave comments or questions for the speakers.