---
tags: v3, project management
---

# Kanban Best Practices Overview

Jotting down ideas here, we can formalize this and add to the Wiki

## Basic Principles

- **Pull system** - Cards/issues move *left to right*
- Look to the left (leftmost is *Backlog*) and pull to the right
- **Workflow** - Move only when requirements are met**
- We have an outline of when cards/issues should move through the board's stages: [v3 Project Statuses](/j98Ildx4TYK_kN4Gqgmqsg)
- Honoring this helps ensure that we can accurately estimate work, velocity, and output
- **Start simple, expand later** - we'll start simple and build a workflow that works for us and expand as we need
- Our tools should work for us and be frictionless
- **One card = one feature/user story/work item**
- We aim to keep our cards clear -- if they become too complex, we should break into multiple cards
- Similarly, if the *effort estimate* is too high this may be a sign that we should break it into multiple cards
- **Be thorough yet concise**
- Our cards should meet our standards for documentation (or we can use templates) to be sure that they have all information needed
- **If Blocked, communicate why** -- if a card/issue is Blocked, let's build a habit of communicating and collaborating to resolve this