Kanban System | Glossary

Definition:

The term  “Kanban” is a Japanese word which means “signal-card” in English and it invented by Industrial engineer “Taiichi Ohno” in order to improve efficiency at Toyota.

In manufacturing environment, this card signals upstream process to produce more.  The Kanban System used as a simple planning system, in which one can control and manage work and inventory at every stage of production optimally. Kanban is a concept identified with Lean and just-in-time (JIT), it is used in the planning which  clearly tells you

  • what to produce?
  • when to produce it?
  • how much to produce?

in a systematic way of approach, that will match inventory with demand and achieve higher levels of quality and throughput.

Application of this in knowledge work, especially in software engineering would enable a sustainable pace and find an approach to introduce changes with minimal resistance.  Kanban System helps to change the focus from a push to meet demand forecasts to a pull generated by actual demand.

Future Reading:

Book: “KANBAN A Successful Evolutionary Change for Your Technology Business” by David J Anderson

https://leankit.com/learn/kanban/what-is-kanban

http://www.everydaykanban.com/what-is-kanban

https://tallyfy.com/kanban-system

Continuous Integration: Improving Software Quality and Reducing Risk | Book Series

Overview:

This book describes how to transform integration from a necessary evil into an everyday part of the development process. The key, as the authors show, is to integrate regularly and often using Continuous Integration (CI) practices and techniques  The author first examines the concept of CI and its practices from the ground up and then move on to explore other effective processes performed by CI systems, such as Database Integration, Testing, Inspection, Deployment, and Feedback. With successful implementation of CI, developers can  reduce their risks and repetitive manual processes, and teams receive better project visibility.

 

This book covers:

  1. How to reduce the amount of repetitive processes you perform when building your software
  2. Practices and techniques for using CI effectively with your teams
  3. Reducing the risks of late defect discovery, low-quality software, lack of visibility, and lack of deployable software
  4. Assessments of different CI servers and related tools on the market.

 

Author:
Paul M. Duvall

Published In:
2007