Similarities between Agile/Scrum and Kanban

Agile	Kanban
Agile project manager	Software manager
Limit work at the iteration level	Limit work (WIP) at the state/phase level
Self-organized and empowered team	Team empowered to make decision on its own

Agile	Kanban
Iteration	No iteration needed
User stories	No user stories needed
Generalist team	Specialist team is OK
New team structure and new roles (PO, Agile Master, development team)	No new team structure and no new roles (whatever exists)
Use velocity as the metric for process improvement	Use lead time as the metric for process improvement
New requirements (user stories) can only be added to the next iteration	Requirements can be added at any time whenever capacity is available
Almost new vocabulary, as in Scrum (Agile project manager, PO, development team)	Whatever current vocabulary is
Item size needs to be broken down to fit an iteration	No item size needs to be broken down
Agile board is reset (after each iteration)	Kanban board is persistent
Cross-functional team	Whatever team structure that exists

Scrum	Kanban
Limit work at the iteration level	Limit work (WIP) at the state/phase level
Self-organized and empowered team	Team empowered to make decision on its own

Scrum	Kanban
No project manager	Project manager is OK
Iteration	No iteration needed
User stories	No user stories needed
Generalist team	Specialist team is OK
New team structure and new roles (PO, ScrumMaster, development team)	No new team structure (no new roles)
Use velocity as the metric for process improvement	Use lead time as the metric for process improvement
User stories can only be added to the next Sprint	Requirements can be added at any time whenever capacity is available
New vocabulary	Whatever current vocabulary is
Items must be broken down to fit a Sprint	No item needs to be broken down
Scrum board is reset after every Sprint	Kanban board is persistent