Geoff Johns (4/7/2015)
I'm not sure that Kanban is the most appropriate tool for career planning: how about a traditional 'list of tasks' or at worst a 'Gantt chart', managed as a sprint or project etc. ...
My understanding is that Kanban is a tool suited to repetitive production, to ensure amongst other things that for a particular assembly (say) task, all the required components are gathered into a 'kit', that they are tested and ready for assembly, and that only the minimum required number of kits are located in the assembly area. Also that there is a minimum back-up supply kit in the stores (safety cover). Additionally, at the supplier of components end, the basis of supply, is one of units of 'complete kits' as needed for the final assembly task.
Happy to discuss ...
Best, Geoff M Johns
From what I've seen, the original aim was a repetitive set of tasks, but it evolved to cover any work items that can be broken down, including management items. The idea is to get a concrete set of items.
I do think it breaks down if too much time is spent determining the tasks, but it can be lightweight. It doesn't need to be exhaustive. For example, if I want to build an application for tracking groceries, I could make Kanban tasks like this:
- create database
- build database table for lists
- skeleton out form for adding items to list
- form for displaying lists.
That's it. However as I start, I realize I need some indexing. If I do it then, fine. If I want to think about it, I add a new task
- create indexes for list table.
It's a work tracking item that I have. As I work, I move these through the status areas (queue, working, done). If I need to add more on the fly, I do. Over time I start to get better at creating new tasks quickly as I think of them and moving them. If I don't need items, or do them right away, I don't bother adding them as work items. That's overhead, which I want to avoid.
This is more about visualizing and tracking the queue of work and work in progress.