Almost every successful Scrum team sooner or later starts using individual Kanban practices – for example, visualization and work in progress limiting. The reverse is also true: every good Kanban team should do daily meetings, retrospectives, and perhaps other Scrum practices.
Kanban is a method based on a pull system of production, that is, a limit on the amount of work in progress. Simply put, everything is arranged in such a way that stagnant tasks can be easily seen and distributed more profitably for the team. This allows you to identify operational problems and motivate employees to improve.
Those who practise Kanban adhere to several key principles:
- reliance on existing methods;
- agreement on incremental, evolutionary changes;
- Respect for the existing order, roles and responsibilities.
If you are already using Scrum and want to add some Kanban practices, these principles will be very useful to you. Kanban practices help to guide the empirical process of inspection and adaptation. However, they do not require the replacement of roles, meetings and artifacts taken in the Scrum Guide.
- Professional Scrum Basics
- Kanban theory and principles
- Kanban in practice: simulations and exercises
- The flow of value and its visualization. Definition of workflow
- Metrics and quantitative process control
- Using Kanban in the Scrum team context