scrum tells you how to work, kanban tells you how to work – Paul Klipp
Similar items
- Both are in line with lean and agile thinking
- Both use "pull" to arrange the schedule
- Both limit the number of jobs in development
- Both drive the process through transparency
- Both focus on early and constant delivery software
- Both are based on self-organizing teams
- Both require a breakdown of work
- In both cases, the release plan is continuously optimized based on empirical data (speed/development cycle)
| Comparison item | Scrum | Signboard |
|---|---|---|
| plan | It has a fixed plan, and it focuses on planning. It starts from the sprint plan and ends with a sprint review, retrospective. Hold daily meetings so that the team understands the next steps, priorities and experience of previous steps. | It has no fixed schedule and no daily meetings. In Kanban, changes can occur at any time, that is, frequent changes. |
| timeline | In scrum, processing a sprint with a fixed duration means providing something to the client after a fixed period of time. | Kanban does not have the concept of sprints, so there is no fixed timetable to deliver products to clients. |
| Task estimation | During the sprint planning period, decide how many activities to extract from the product backlog and add the sprint backlog. For example, if the sprint lasts for two weeks, choose the number of activities in such a way that they can be completed within the sprint, that is, within two weeks. | It does not estimate the task. |
| Adaptability | This method is suitable for large projects, because large projects can be divided into multiple sprints. | It is mainly suitable for small projects. |
| Work restriction | Indirectly restrict the work in development (each iteration) | Set limits for work in development (per workflow status) |
| keep changing | In Scrum, constant changes can be easily adjusted in a short sprint. | If any major changes occur, the Kanban method fails. |
| Task change | No new tasks can be added in the iteration | As long as the productivity allows, you can add work tasks at any time |
| cost | In Scrum, the task is estimated, that is, a fixed number of activities are taken in the sprint, so the total cost of the project is minimal. | In Kanban, tasks are not estimated, so the total cost of the project is not accurate. |
| Roles and responsibilities | Product owner/Scrum master/Team) In Scrum, the Scrum Master assigns specific roles to team members, and the product owner informs the team members of the product goals that they must work on. | No predefined roles are assigned to team members. All team members are responsible for cooperating to provide valuable products. |
| team | Designate a cross-functional team | No cross-functional team is specified, and dedicated teams are also allowed |
| Cross-team | A single team is responsible for the Sprint backlog | Share the board with a team and members |
| Productivity measurement | Measure productivity by using cycle time or the time it takes to complete the entire project from start to finish. | Use speed to measure productivity through sprints. |
| Release method | A small version is released after each sprint. | It provides continuous delivery. |
| Kanban cycle | The Scrum board is reset after each iteration | Kanban reflects persistent development |
| priority | Prescribe prioritized proiduct backlog | Priority is optional |
refers:
https://www.yiibai.com/jira/jira-kanban-vs-scrum.html
https://www.tapd.cn/forum/view/36701