Jim spoke at Oredev in Malmo, Sweden, in November 2010 on The Psychology of Kanban and Personal Kanban and the Individual Coder. Click on the links below to see the video.
Clarity Means Completion: The Psychology of Kanban:
Clarity Means Completion: The Psychology of Kanban – Jim Benson
Personal Kanban and the Individual Coder:
Personal Kanban: Optimizing the Individual Coder – Jim Benson
Jim will be in Phoenix for Agile Alliance’s Scrum Beyond Software conference where his is planning to discuss his use of agile techniques with the United Nations, the World Bank, and in non-software groups in several industries.
A basic Personal Kanban on the iPhone or iPod Touch
You asked for it, and we listened. Today we are proud to announce the launch of the first Personal Kanban iPhone app, iKan.
When we set out to build it, we decided to focus on a few key things:
1. Small Screen Many Tasks - We wanted to make the best use of the screen real estate on the iPhone, so we built the app vertically.
2. KISS - We wanted the initial release to be extremely basic. In future updates we will respond to YOUR needs, and additional features will be based on YOUR input. So please keep us posted as to the direction you’d like to see iKan take. We already have a long list of upgrades in our pipeline, but are primarily interested in how you are actually using the app.
3. Use Your Data - Integration with other popular time- and backlog-management tools. In the first version, we have importation from Zen. (But we can only import your data). If you import a project from Zen, you will bring that project’s value stream with it.
4. Start with Basics then Build to Suit - Each iKan starts with an entry-level Personal Kanban value stream with Ready / Doing / Done sections. You can however, create your own column headings and set your own WIP limits.
In the coming weeks, we’ll have a series of short tutorial videos for iKan – so stay tuned!
Special thanks to Jeremy Lightsmith, Gary Bernhardt and Corey Ladas who were all vital in making iKan a reality.
Get your copy of iKan at the iTunes Store.
For more information on Personal Kanban, see the Personal Kanban web site.
Conversation Creates Knowledge
Over the last few months, I’ve had the good fortune to be a featured guest on three different podcasts discussing Personal Kanban. In the Yi-Tan calls, we discussed Personal Kanban and Personal Kanban for teams. In the Social Media Breakfast Seattle Podcast, we explored the relationships between Lean thinking and social media. Of course, Personal Kanban comes up there as well.
Yi-Tan Call #261 – Personal Kanban With Jerry Michalski’s group, I discuss Personal Kanban, how it started, and how it works.
Yi-Tan Call #268 – Personal Kanban for Teams Again with Jerry’s virtual roundtable, I discuss how Personal Kanban and other kanban applications work for teams, groups, and organizations.
For Social Media Breakfast Seattle Lean Management and the CIA Heidi Miller interviews me about lean management, social media, Personal Kanban, and what’s happening in the Intelligence Community.
Later this month I’ll be featured on the Business 901 podcast, talking even more about Personal Kanban, but this time interviewed by Joe Dager, who focuses on marketing and lean principles.
When: November 17, 2009
Where: Twitter
Hashtag: #pkflow
Modus and personalkanban.com are hosting a “Tweet-a-ban.” Whether you’re a Personal Kanban practitioner or just have an interest in improving your productivity, join in on the asynchronous, 24 hour long global conversation. For details click here.
Modus Cooperandi is pleased to announce the release of its second Personal Kanban InfoPak. In Personal Kanban 101: Achieving Focus & Clarity with Your First Personal Kanban we discuss the essentials for getting your board started. Topics addressed include how to establish value stream, backlog and WIP, and why there are only two hard rules to implementing this productivity tool.
As always, please feel free to download, distribute, comment and let us know what you think.
This is the first in a series of Modus Cooperandi’s InfoPaks. They are downloadable, and work like a narrative whitepaper. Think of them like graphic novels for business.
In InfoPak One: Personal Kanban at the World Bank, we discuss the experience we had leading a rapid development project at the World Bank, specifically, how visual controls work with small groups, and why they are preferable to traditional team management.
This InfoPak is best read by clicking the “Full” button above. It’s also designed to be downloaded to distribute to others. Over the next few weeks, we will post more InfoPaks on Personal Kanban. Please feel free to comment and let us know what you think.
World Bank in Washington DC
Modus Cooperandi is excited to announce our upcoming personal kanban project, where we will use our Personal Kanban techniques in a directed exercise with knowledge workers from around the world. From the 21st through the 25th of September, Jim Benson and Tonianne DeMaria Barry will be working with The World Agroforestry Centre and the World Bank to lead their Capacity Building Program on the Opportunity Costs of Reducing Emissions from Deforestation and Land Use Change (OpCost) Writeshop, at the World Bank Institute in Washington D.C. The intent of this directed exercise is to create a comprehensive technical document. As small working groups and as a unified team, participants will use personal kanban to maintain project coherence and track completion. The project is expected to achieve rapid release of a highly technical product by knowledge workers from around the world. The multi-lingual, multi-disciplinary group will benefit from personal kanban’s visual controls and work flow.
We will be blogging and tweeting about the event as it unfolds.
Photo: Brixton
A kanban is a tool to visualize, organize, and complete work. The first official use of kanban can be traced to Taiichi Ohno’s work at Toyota. He needed a way to quickly communicate to all workers how much work was being done, in what state it was, and how the work was being done. His goal was to make work processes transparent – meaning he wanted everyone, not just managers to know what was “really” going on. The goal was to empower line workers to improve how Toyota worked. Everyone had a hand in making Toyota better.
Work moves across a kanban
In the image to the right we see two work flows with work flowing through them. The top part of the board shows three states: Backlog, Doing, and Done. Tasks move across this simple workflow.
In a subtle way, this is doing three main things:
That’s it! That’s all there is to a kanban physically.
For personal kanban, we take the simplicity of this system and use it to help us understand how we do what we do and how long it takes to do it. Simply having clarity around our workload is a tremendous psychological gift.
The basic kanban: Waiting, Working, Done
A quick trip through personal kanban design patterns demonstrates how they can be created using any number of materials. This tutorial illustrates how to build the most common personal kanban.
Step One: Establish Your Value Stream
Value Stream (v
l
y
str
m): The flow of work from the moment you start to when it is finished. The most simple value stream possible is Backlog (work waiting to be done), Doing (work being done), and Done (yes, that’s right, work that’s done). While you can set this up on a white board or even a piece of paper, a white board is preferable. Why? Because as you grow to better understand your value stream, you will want to change your kanban. You will add steps, or refine how you think about work. A white board provides permanence, yet allows ultimate flexibility: you can always erase and draw something new.
Step Two: Establish Your Backlog
Backlog (bkl
g
, -lôg): The work you haven’t done yet. All that stuff you need to do that you haven’t done – that’s your backlog. Everything you need to do, start writing it down onto Post-its. Big tasks, small tasks, get them all down. Write them onto post-its and start populating your backlog. Don’t sweep things under the rug. Don’t lie to yourself. Your first backlog-fest should be a painful experience. You should, at some point say, “god, there’s way too much of this.”
Step Three: Establish Your WIP Limit
WIP (hw
p, wp): Work in Progress Limit – The amount of work you can handle at one time. We have a tendency to leave many things half-done. Our brains hate this. Part of what makes kanban work is finding the sweet spot, where we are doing the optimal amount of work at the optimal speed. Set an arbitrary number in the beginning, let’s say no more than 5 things. Add this number to your Doing column.
"Pull" tasks from one kanban stage to the next
Step Four: Begin to Pull
Pull (p
l): To take completed work from one stage of the value stream and pull it into the next. You’re ready to go! That’s right – step four is Begin Working.
Beyond Step Four: Prioritize, Refine, and Reduce
Past step four, it’s all about prioritization of work, refinement of the value stream, and reduction of waste.
