progress.
In knowledge work, the components of production are ideas and information [10, 11]. In software and
systems, the kanban concept has evolved into a means of smoothing flow by balancing work with
resource capability. It focuses more on limiting work in progress according to capacity. Work cannot be
started until there is an available appropriate resource. In that way, it is characterized as a “pull” system,
since the work is pulled into the process rather than “pushed” via a schedule. In this research, we define a
visually monitored set of process steps adding value to work units that flow through them. Each step has
its own queue and set of resources. The fact that queues are included in the system allows costs of delay
and other usually invisible aspects of scheduling to be integral inputs to decision making. The visual
representation of the work is critical to kanban success, because it provides immediate understanding of
the state of flow through the set of process activities. This transparency makes apparent process delays or
resource issues and enables the team to recognize and react immediately to resolve the cause. on. The
process is managed through Work in Progress (WIP) limits, small batch sizes, and Classes-of-Service
(COS) definitions that prioritize work with respect to value and risk. Flow is measured and tracked
through statistical methods that provide insight to tune and improve the system