Скачать или смотреть Scrum vs Kanban

Definition
Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.

Kanban is a popular Lean workflow management method for defining, managing, and improving services that deliver knowledge work

What they focus on?
Scrum focusses on empirical process control i.e., Being Agile, and if done rightly it may help improve your processes.

Kanban focusses on improving your processes, and if done correctly, it may result in you Being Agile.

How they work?
Scrum is framework specially designed to support you practice empirical process control & lean principles. All the scrum events and artifacts help you Inspect & Adapt your emergent work and processes.

Kanban is a pull based signaling system which is based on visualizing the workflow of the knowledge work on a Kanban board. With the help of the visualization, kanban team identifies bottlenecks, improvement opportunities & improves the Flow of work.

Principles
Scrum is based upon the principles of Empiricism and Lean thinking. Empiricism and 3 pillars, namely Transparency, Inspection & Adaptation. Scrum has 5 values which the team must embrace, they are Commitment, Courage, Respect, Focus and Openness.

Kanban originates from Lean principles, and has 5 principles namely: Visualize the workflow, Limit work in progress, Manage flow, Make process policies explicit, Establish feedback loops and Improve collaboratively.

Roles and Events
A Scrum Team comprises of a Product Owner, a Scrum Master and Development team members

Kanban does not suggest specific roles or team composition, more than a cross functional team. Based upon the need’s roles can be added or adjusted.

Scrum as 5 events namely: Sprint, Sprint Planning, Daily Scrum, Sprint Review & Sprint Retrospective.

Kanban does not suggest any events, the team may decide on the event based on their needs.

Suitability
Scrum is most suited when the team is building a complex product, when the domain in general is complex.

Though Kanban is suitable for any project, but in real life teams working on either on something that doesn’t fit for Scrum, such as a domain where a team cannot work together by having a common goal or on something that is not complex are an excellent candidate for Kanban. However, Kanban is equally suited for complex work.