Posts filed under: Kanban Development

Kanban Development

This page contains posts by Jayme related to developing software using the Kanban development methodology.

Taiichi Ohno of Japan helped Toyota dominate the U.S. automobile industry through the introduction of several improvements to manufacturing processes. His system of processes became known as the Toyota Production System, or TPS.

In the early 2000s, software development teams began adopting some of the practices of TPS for use in producing software. The primary practice usually associated with TPS on software teams is the use of a Kanban board.

Kanban development operates under the assumption that there is more work to be done than can be forecasted and assigned predictably. Changes in market demand and business needs on a software project necessitate adaptability.

Teams use a visual board to indicate tasks to be completed, and allow team members to select a new task as soon as they are done with the prior one. There are typically “swim lanes”, or vertical separations between the various stages a task goes through before released to customers. This helps identify bottlenecks and optimize production of software.

Other software developers often disagree with us about what processes to use due to how uncertainty impacts software development....
I'll help you understand how to decide between scrum and kanban, so you can make a decision that lets you deliver products in a lean fashion....
I'll help you understand how software estimation effects the expectations between the business and development, and how to think about it in a lean fashion....