10. Why is there no done column?
Kanban is flexible for your workflow. My approach is keeping my board lean and clean. When I close an issue I enjoy removing it immediately. My suggestion is; that you do you.
My personal Kanban setup is simple. I put tasks (issues) into three columns; backlog, in progress and waiting. An issue is a simple unit of work. If an issue has multiple parts then consider it as multiple issues. It will make managing WIP more effective.
https://t.co/sJKJABjyeJ
If you've never heard of Kanban, Wikipedia https://t.co/MMepSSSCNt provides a good overview.
I use Kanban because...
• It scales to any size project.
• It’s a framework and can be incorporated into existing processes.
• It has one rule; limit work in progress (WIP).
Waiting
When an issue requires approval or input from someone I pull it into my “Waiting” column (aka follow-up). While it's waiting a new issue can be pulled into WIP or not. Treat “waiting”, the same as WIP. Don't let issues stall waiting for feedback.
In Progress
Kanban has one rule; manage work in progress (WIP). The best practice is to limit WIP to 3 issues. This maintains focus and flexibility for multiple priorities. An issue remains WIP until it is complete or requires action from a 3rd party.
https://t.co/sJKJABB9Dj
What is this issue dependent on?
Often there is a sequence to completing an issue depending on other issues being done first. An issue can be “blocked by” or “blocking” another issue.
https://t.co/sJKJABjyeJ
Who is the best person to work on the issue?
Are you the best person for the issue? If you break an issue into smaller issues perhaps it can be delegated to one or more people. This frees you to work on another issue and increases velocity for getting to what’s next.