EXIN Kanban Foundation study plan
EXIN Kanban Foundation · Give each week a clear focus.
8 weeks · About 6 hours per week
Kanban
Define Kanban in your own words and list the core practices it is built on, without consulting notes at the end of the week
Identify the problems Kanban was created to solve and describe how it differs from a traditional stage-gate or waterfall approach
Sketch a simple value stream for a process you know and mark where work waits versus where work is actively transformed
Explain the difference between push and pull systems and give one concrete example of each from everyday work
Your checkpoint
A one-page written summary covering the definition of Kanban, its core practices, push versus pull, and a hand-drawn value stream map of a real or realistic workflow
Kanban
Map the workflow steps of a chosen process and define explicit policies for entry and exit of each step
Identify the work item types in that process and describe what makes each type distinct
Establish a definition of done for at least one work item type and test it against real examples
Explain why visualizing work is treated as a foundational practice rather than an optional nicety
Your checkpoint
A workflow board diagram with named columns, written entry and exit policies per column, and a definition of done for one work item type
Kanban
Explain what a work-in-progress limit is and why limiting WIP changes system behavior
Describe how a pull system operates when a WIP limit is reached and what the correct response is
Calculate the effect of reducing WIP on cycle time using Little's Law with a worked example
Diagnose a board without WIP limits and propose specific limits with justification
Your checkpoint
A worked Little's Law example plus a proposed set of WIP limits for the week 2 board, each limit justified in two or three sentences
Kanban
Define lead time and cycle time and distinguish them precisely with a timeline diagram
Measure cycle time for at least ten work items from a real or simulated data set
Build a cycle time scatter plot and interpret its shape and spread
Explain how flow efficiency is calculated and what a low value indicates
Your checkpoint
A metrics pack containing a lead time versus cycle time diagram, a ten-item cycle time data set, a scatter plot, and a calculated flow efficiency figure
Kanban
Construct a cumulative flow diagram from the week 4 data and read its bands correctly
Identify bottlenecks and queue buildup from a cumulative flow diagram and propose countermeasures
Explain the relationship between WIP, throughput, and cycle time as shown by the diagram
Describe how classes of service and explicit policies affect how work is selected and prioritized
Your checkpoint
A cumulative flow diagram with a written interpretation identifying at least two bottlenecks and one countermeasure for each, plus a short note on classes of service
Kanban
Explain the purpose and mechanics of feedback loops in Kanban, including daily standups and replenishment or review meetings
Describe how service delivery reviews and operations reviews differ in purpose and cadence
Outline how a Kanban system is introduced incrementally, starting from the current state
Explain how Kanban fits alongside existing methods such as Scrum or a stage-gate process without replacing them
Your checkpoint
A one-page introduction plan describing the feedback loop cadence, meeting purposes, and a phased rollout sequence for a team adopting Kanban
Kanban
Define the change management principles that underpin Kanban and explain why starting with the current state matters
Describe the role of the Kanban board as a shared model and how it evolves over time
Explain how improvement is driven empirically from observed flow data rather than prescribed process change
Work through at least thirty practice questions across all topics and log every wrong answer with the reason
Your checkpoint
A practice test log of at least thirty questions with a categorized error list and a written paragraph on how Kanban drives evolutionary change
Kanban
Review every logged error from week 7 and rewrite the underlying concept in your own words
Rehearse the full syllabus by producing a one-page summary of each major topic area from memory
Complete a timed full-length practice set and score it against your week 7 baseline
Identify your three weakest areas and close each with a targeted review session
Your checkpoint
A final revision sheet of one-page memory summaries per topic area plus a scored timed practice result compared against the week 7 baseline
Milestones
Week 2: You can draw a Kanban board from memory, name each column's policy, and explain why visualizing work is foundational without referring to notes
Week 4: You can distinguish lead time from cycle time on a timeline, calculate flow efficiency, and interpret a cycle time scatter plot without prompts
Week 6: You can read a cumulative flow diagram, identify a bottleneck from it, and explain how feedback loops and cadence keep a Kanban system improving
Week 8: You score at or above your target on a timed full-length practice set and can summarize every major topic area on a single page from memory