October 30, 2009
For a few months I’ve been using a personal kanban board as a way to becoming more effective, efficient and knowledgeable about the process that goes into my work. It’s only been used for hobby and home projects, because that’s where I felt had lost control and stuff just kept piling up.
I’ve always known that my main problem was initializing too many projects only to become stressed out by everything, unmotivated and abandoning most of them halfway through, which in turn led to a sense of failure and broken promises, either to myself or to others. Therefore the Work In Process (WIP) limitations of a kanban board seemed like a very good idea, and I quickly set one up for free at Zen. After adding some WIP limitations to the Working column, I got started and the results came instantly: I’ve been finishing up some old projects that I’ve had in the back of my mind for years. All of a sudden I know that when I start a project, I will finish it. Even if it becomes stale or boring, I have to push through before I can move on to something that seems like more fun. Just knowing that is a great motivator for actually finishing stuff, thereby delivering some kind of value.
My kanban board is very simple: I have a backlog, a Working column, a Complete column and an archive (where items I’ve finished long ago go). It seems almost too simple compared to what large teams use, but hey – there’s no team in I (and vice versa). The Working column has a WIP limit of 2 items, of which one can be computer related (e.g. reading the RSpec Book) and one can be related to something else (e.g. painting the walls). I noticed that if I allow myself to do two or more computer related tasks at once, I jump back and forth depending on the mood. That in turn leads to the pace feeling a bit slow, which lowers the motivation to work on stuff even more, which makes the pace even slower and so on…
I’ve actually completed many more items than are in the Complete column above. I’ve just moved them into the “Archive” column. Just so you know.
Since I only have three columns, the visualization part of the kanban isn’t as prominent as when you’re working on a bigger team. Neither the backlog nor the Complete column can be bottlenecks, all I have to analyze from this perspective is the Working column, and it’s always full. I tried having more columns in the beginning, just to be able to identify bottlenecks, but it always felt contrived.
So the steps for you to get started with a personal kanban are very few:
- Create a board with columns and determine the initial Work In Process limits (you can change them later, it’s an open process).
- Create tasks/stories and put them in the backlog.
- Start pulling from the backlog.
- Analyze what goes well and what doesn’t, and start reaping the benefits of actually getting things done. It sure feels good pulling items into that column.
Once those darn walls are painted, my fiancee and I will put up a common kanban board for both of us in that room (the guest room/office). I’ll report on that in a future blog post.