It depends and it could be both where you utilize the Scrum framework but incorporate some key principles and tools of Kanban.
Both have their places so define your appropriate way of working based on the context faced by the team.
Kanban does lend itself equally well to operational work as it does to project-type work. For example, handling service requests in a continuous flow model is possible with Kanban but more challenging with Scrum given that sprint durations can only be reduced so much before you are no longer able to follow the Scrum framework.
I have found that Kanban tends to be more of an evolutionary approach but that is sometimes misinterpreted to mean that dramatic change is not possible with it. In reality, if the team recognizes something is wrong, they should be empowered to fix it regardless of the approach we are following.
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
Yolanda
I think the two together brings the best of the two worlds. Few years ago, scrum.org came up with a credential called: “Scrum with Kanban” and when I was studying for the certification, I came to realize many things in terms of how Kanban principles and tools can do compliment those of scrum which is what Kiron mentioned as well.
RK
...
1 reply by Yolanda Morales-Wong
Mar 19, 2023 5:59 PM
Yolanda Morales-Wong
...
Good to know.
Saving Changes...
Mehdi AlibakhshiPM Specialist and Instructor| PHSABritish Columbia, Canada
Yolanda
The choice between Scrum and Kanban largely depends on the organization's specific needs, preferences, and circumstances, team size, project complexity, and organizational culture also play a significant role.
Scrum is a structured framework that emphasizes time-boxed sprints, with clear roles, ceremonies, and artifacts. This structure can help teams to stay focused, reduce waste, and increase transparency, which can lead to greater efficiency. However, Scrum can also be more rigid and less adaptable to change than Kanban.
Kanban, on the other hand, is a more flexible approach that emphasizes visualizing and optimizing the flow of work. This flexibility can allow teams to adapt quickly to changing circumstances and to continuously improve their process. However, this lack of structure can also lead to inefficiencies if the team is not careful to manage their work in progress, limit bottlenecks, and prioritize their work effectively.
In the end, the choice between Scrum and Kanban, or even a hybrid approach like Scrumban, should be based on the needs and goals of the organization, the team's context, complexity, and culture.
I think the two together brings the best of the two worlds. Few years ago, scrum.org came up with a credential called: “Scrum with Kanban” and when I was studying for the certification, I came to realize many things in terms of how Kanban principles and tools can do compliment those of scrum which is what Kiron mentioned as well.
Yolanda
The choice between Scrum and Kanban largely depends on the organization's specific needs, preferences, and circumstances, team size, project complexity, and organizational culture also play a significant role.
Scrum is a structured framework that emphasizes time-boxed sprints, with clear roles, ceremonies, and artifacts. This structure can help teams to stay focused, reduce waste, and increase transparency, which can lead to greater efficiency. However, Scrum can also be more rigid and less adaptable to change than Kanban.
Kanban, on the other hand, is a more flexible approach that emphasizes visualizing and optimizing the flow of work. This flexibility can allow teams to adapt quickly to changing circumstances and to continuously improve their process. However, this lack of structure can also lead to inefficiencies if the team is not careful to manage their work in progress, limit bottlenecks, and prioritize their work effectively.
In the end, the choice between Scrum and Kanban, or even a hybrid approach like Scrumban, should be based on the needs and goals of the organization, the team's context, complexity, and culture.
Thanks for your response. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Both are totally different things. Kanban is oriented to flow. Scrum is oriented to batch or iterations. In Scrum after each iteration the team has to deliver something working (no matter you use it for software or non-software products). This is not needed in Kanban. At the end, the first thing to do is, to put this in terms of the PMI, perform the needs assessment activity which belongs to business analysis theory to define the solution after understanding the current situation and the future situation, where solution is equal to "the thing" to be created plus "the way" to create it.
Both approaches obtain the result, however, scrum works well in the project such as developing apps and technology fields because it requires a time-boxed sprint to achieve desirable results. You could also define different variables to determine whether to use one of them or mix for example, look at company culture, team size, project scope and its complexity and others. Saving Changes...
Community Champion
