Dependencies are things that occur in succession. One thing happens, then another thing can happen. Ideally, on a kanban, the value stream will visualize these transitions. For a value stream like this:
Analysis -> Creation -> Refinement -> Launch
refinement is dependent on both analysis and creation.
That neatly takes care of dependencies, but in our Personal Kanban we really don’t want to have to come up with new value streams for every little project we are doing. So we need to come up with ways to visualize dependencies that will let us maintain a simple value stream.
So let’s look at a few ways we can do that. As always, these are suggestions and we’d love to see how other people work this out.
Task Notation
We can simply notate tasks with where they lie in a stream of pre-requisites. Noting what comes before can help us not prematurely pull a task, letting us know what comes next can help us raise that next task in priority ones it’s antecedent task is completed.
Scheduled Escalation
Sometimes tasks become relevant on or around a specific date. What we can do is place tasks that need escalation on a certain date on an actual calendar. When that date comes, take the task off the calendar and place it in backlog. If is has a due date, be sure to note that date on the sticky.
Sticky Stacks
Tasks that neatly follow one another can simply stack. When a task is pulled, its next task is seen in the backlog. Sticky stacks can also nicely visualize a project without taking up too much space.
–
So that’s it. Some quick ways to deal with dependencies outside the value stream. Of course, do look in Design Patterns to see if you can find ways to deal more elegantly with specific projects.
I like it!
I am inclined to use sticky stacks but had trouble with what gets put out of sight. I think I will look for clusters, because often dependencies are inter-cluster and the in-cluster ones are simply sequential.
I need to deal with multiple streams also. My computer infrastructure needs serious updating, and that includes migration of data, retirement of some machines, planning upgrades, etc. Meanwhile, I have to move off of Blogger before they cease support for publishing to my own site by FTP on March 26, and this impinges on infrastructure work. And then there are the billable projects, stansdards-devvelopment work, dealing with tax season, veterinary schedules, … [;<).
I am not sure what to do about the calendar business. It's a wall-space and visibility problem for me. My best calendar attention is in Outlook, and I will need to be creative about connecting between that calendar and items on my physical Kanban display.
Thanks, this gives me plenty to think about and to try out as I reshuffle my PK display today.
Multiple projects, deadlines, grouped dependencies …
Difficult to visualize, but worse yet if not visualized.
Looking forward to seeing how your PK turns out.
For those who are dealing with multiple projects where they need to collaborate but still want as much post-it simplicity as possible, I came across Action Method software recently and have been trying it out. It looks promising. Getting the balance of ‘just enough’ complexity to get the job done seems to be one of the major challenges in knowledge work. BTW I loved your INFOPAK slide decks
Thanks so much for your comment, John. I enjoy using Action Method’s paper products and will be sure to check out their software. How exactly are you using it? As an online kanban?
Happy to hear you enjoyed our Infopaks. Once the book is completed (we’re getting close) we’ll be releasing several other slide decks, so stay tuned!