Reading the initial definition "Kanban is a simple scheduling system used to achieve Just In Time (JIT) delivery of products" tells a lot about the authors understanding of Kanban. At least the understanding is not in line, with what the "inventor" of Kanban - David Anderson - says about his system (measure and optimize cycle time). Also the initial explanation of how to implement Kanban (first workflow, than priority setting, set WIP, set core rules ...) is not in line with Anderson (1. Improve quality, 2. Reduce WIP, 3. Deliver frequent, 4. Balance demand and capacity, 5. Prioritise, 6. Analyse variability to improve predictability).
To get familiar with Kanban definitely not recommended.