All three methodologies adhere to the principles laid out in the Agile Manifesto which aims at providing as much value to customers as possible in the time available. The differences between them are a result of trying to uphold the Agile principles in radically different contexts.
Kanban is a really useful way for teams with a continually changing backlog of items to increase efficiency by limiting the amount of work-in-progress, whilst respecting existing roles and responsibilities.
Scrum is more suitable for teams who can devote their collective time to a project or product. It brings much more in the way of structure to help teams make major productivity gains through frequent communication and planning while still providing the freedom to decide among themselves how to engineer solutions.
XP adds another level of sophistication, bringing a strong focus on quality by insisting on a set of core engineering practices that keeps code clean and software stable.
– https://manifesto.co.uk/
Optimizing your Production by Adapting Scrum to the Non-Digital World
