Kanban vs Scrum pros:
- Extremely flexible. Focus on individual tasks allows to quickly alter the direction of development.
- Has fewer processes than Scrum: easy task prioritization eliminates idle time.
- Works even for larger teams.
- Better suits service-oriented teams.
- Ideal for the maintenance phase (or situations where you have a continuous stream of change requests)
- Allows to work on one task at a time. The team doesn’t have to re-plan activities when the client changes priorities.
Kanban vs Scrum cons:
- No Sprint planning makes it harder to make predictions regarding the release dates.
- Project scope can be difficult to control.
- Engineers might have trouble prioritizing the incoming tasks (self discipline is essential).
- No timeboxing might lead to lower productivity.
- Easy to lose the end-goal of development.