Get flash to fully experience Pearltrees
Posted by Kenji Hiranabe on Jan 14, 2008 Sections Process & Practices ,
Kanban is a lean approach to agile software development. Actually, Kanban means many things. Literally, Kanban is a Japanese word that means “visual card”. At Toyota, Kanban is the term used for the visual & physical signaling system that ties together the whole Lean Production system. Most agile methods such as Scrum and XP are already well aligned with lean principles. In 2004, however, David Anderson pioneered a more direct implementation of Lean Thinking and Theory of Constraints to software development.
The Kanban app gives teams the option of managing pull-based, Lean software development projects alongside other iterative and time-boxed projects. Kanban originated from the Toyota Production System. Taiichi Ohno wrote in his Toyota Production System book, "The two pillars of the Toyota production system are just-in-time and automation with a human touch, or autonomation. The tool used to operate the system is kanban." View Larger
After hearing about Kanban as an Agile method for managing workflow at the excellent DevOpsDays ‘09 conference , I was immediately struck by how well it fits the workflow of tasks that we face in our team. After a brief discussion with my MD (’we need to manage our workload better, and Kanban seems a good fit. It means we will be limiting how many tasks can be on the go at any given time though – but we’ll get more done overall, and you’ll see what we are doing on a big board’) to get his buy-in on the Work-In-Progress (WIP) limit, my team and I got together to plan what the board should look like – and get it in action! Firstly, a little background on $WORK and in particular my team within it. The core business is web development for our clients, who are mostly large academic publishers, though we also offer hosting and systems management solutions to provide a full managed solution for them. I head up the hosting and support side of the business.
comments Applying Kanban to IT Processes (Part 2) by Eli Weinstock-Herman (tarwn) on Dec 08, 2009 in categories IT Service Management , Project Management , IT Processes Instapaper