Kanban's Fo' Everyone!

At Turing, the pace moves so quickly that I wish I had the luxury of more time or could even be granted a do-over. That is unfortunately not the case for many aspects of life, let alone a fast-paced code school. So what are the options for dealing with a fast-paced environment? I have found myself thinking about this topic more and more as time goes on, and I believe I have found an answer. The solution is not as easy as pausing time in the way that so many books and movies have made it seem. Instead, the solution deals with managing all of the assignments, errands, and tasks that life provides as soon as possible. I do not mean that all of these tasks should be completed right away, just simply managed. A simple way to accomplish all tasks would be to adopt the Kanban Board, a workflow cycle utilized by both manufacturing and software companies. The Kanban Board was originally used by Toyota during manufacturing in the 1940s. In Japanese, Kanban means “visual signal.” The meaning is the foundational property that has kept the Kanban Board a useful resource for so long. It was used to visually pass messages relating to progress down an assembly line by Toyota. Now, it can be used in group assignments or implemented by a single individual as I plan to do. The Kanban Board may sound like a huge piece of beautiful wood, but it can really be anything from a poster, whiteboard, or even some tape on the refrigerator door. But every board must have three vertical columns with the titles “to-do,” “in-progress,” and “done.” Once the layout is complete, one would simply need to write all of their tasks out onto separate note cards or sticky notes. Next, one...
Read Full Article
Upload Background Image
Drop File