Great look at the similarities and differences between Scrum and Kanban. Good to know that you can use both Kanban and Scrum together and not have to choose between them.
Indeed, as the Scrum Guide says, "Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems." And that's any problem, not just the field of software development!
At first sight I tend to think that kanban is well suited for a team mantaining an existing product, while I see scrum more valuable in developing a brand new (and complex) product
My experience is that you can use the differing features of Kanban and Scrum in order to address the situation that you are in. if you are extremely time-strapped or are losing resources, go for Kanban. Kanban does not make you commit to a "sprint goal" (because there are no sprints). if you have a lot of work ahead of you that you know about, and you have a "due date" that is at least 4 weeks away, you might as well chop up that time into actual sprints. The reason WHY is because focusing on incremental goals WILL HELP you move forward at a better pace than just having a giant amorphous backlog, refined or not. It will also HELP THE PRODUCT be more robust as you are then able to deliver on sprint goals (when they are reached) and solicit feedback and test in those sprint increments. Scrum has the overhead of sprint planning. This overhead is easily seen: you need the time for the sprint planning meetings, and you need more relatively consistent development resources. Kanban does not have this overhead. The most important thing to keep in mind is that whether it is Scrum or Kanban, REFINEMENT REMAINS. Refinement is a heavyweight contributor to having a healthy team, a decent pace, and a product aligned with the desires of your stakeholders and the capacity of your team.
A review is where you review the work that's been done in the Sprint, usually along with the Stakeholders, and decide how to proceed next with the work in the backlog. A retrospective is where you look at how to improve as a Team. Are there things that you are doing that are not working, and so you will usually come out of this with some action points. It's also an opportunity to look a things that have gone well and come together as a Team and celebrate success
Only one correction I would like to make. Scrum sprints are supposed to be two weeks or under in length. Scrum is a way or organizing the development strategy and maintaining regular evaluations that can provide valuable information up the management chain. Kanban is a method of task management. That is why they work so well together.
First, you pronounced Kanban wrong. 🤦♀ But on the other points, you're 100%. Technically the Scrum Guide says 1 month or less, but 2 weeks is the typical sweet-spot I see. I'm actually going to redo this video as I want to make a few changes, like what you suggest. Hopefully I can still get my point across in a very short video.
Oooooh nice. Kanban is actually not a "framework" like Scrum is...which is why Kanban works well with Scrum. Kanban does have cadences like retros and reviews...but not sprint based as you said...glad to see more and more ppl getting out of that "Versus" mindset!
Yeah, it's touchy on how exactly you describe it, as some people reject 'process', some reject 'methodology' and some reject 'framework.' I just felt 'framework' was safe. Scrum definitely describes itself as a framework. Thanks for the feedback!
In reality most Scrum teams don’t follow it slavishly, especially not if a critical bug shows up. Some flexibility is always needed, but I do like that Scrums gives some stability and it is nice when the team is able to come together at the start and the end of the sprint.
![Felix "Unfair" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/Oswujxm2Ag0/mqdefault.jpg)
Great look at the similarities and differences between Scrum and Kanban. Good to know that you can use both Kanban and Scrum together and not have to choose between them.
Please note that Scrum is used well beyond software. It started in software and is now used in almost any type of product creation.
Indeed, as the Scrum Guide says, "Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems."
And that's any problem, not just the field of software development!
fuck scrum
At first sight I tend to think that kanban is well suited for a team mantaining an existing product, while I see scrum more valuable in developing a brand new (and complex) product
The difference between Scrum and Kanban has never been so clear. Thanks!
Thanks Cameron2. 🤣🤣🤣
Very helpful insights, Thanks so much!!
Very good analysis of the two methodology - Kanban and Scrum. Thank you very much.
Love this discussion of Kanban, Agile and Scrum.
My experience is that you can use the differing features of Kanban and Scrum in order to address the situation that you are in.
if you are extremely time-strapped or are losing resources, go for Kanban. Kanban does not make you commit to a "sprint goal" (because there are no sprints).
if you have a lot of work ahead of you that you know about, and you have a "due date" that is at least 4 weeks away, you might as well chop up that time into actual sprints. The reason WHY is because focusing on incremental goals WILL HELP you move forward at a better pace than just having a giant amorphous backlog, refined or not. It will also HELP THE PRODUCT be more robust as you are then able to deliver on sprint goals (when they are reached) and solicit feedback and test in those sprint increments.
Scrum has the overhead of sprint planning. This overhead is easily seen: you need the time for the sprint planning meetings, and you need more relatively consistent development resources. Kanban does not have this overhead.
The most important thing to keep in mind is that whether it is Scrum or Kanban, REFINEMENT REMAINS. Refinement is a heavyweight contributor to having a healthy team, a decent pace, and a product aligned with the desires of your stakeholders and the capacity of your team.
Good presentation. Thanks.
You are welcome!
What’s the difference between a review and retrospective?
A review is where you review the work that's been done in the Sprint, usually along with the Stakeholders, and decide how to proceed next with the work in the backlog. A retrospective is where you look at how to improve as a Team. Are there things that you are doing that are not working, and so you will usually come out of this with some action points. It's also an opportunity to look a things that have gone well and come together as a Team and celebrate success
Only one correction I would like to make. Scrum sprints are supposed to be two weeks or under in length. Scrum is a way or organizing the development strategy and maintaining regular evaluations that can provide valuable information up the management chain. Kanban is a method of task management. That is why they work so well together.
First, you pronounced Kanban wrong. 🤦♀
But on the other points, you're 100%. Technically the Scrum Guide says 1 month or less, but 2 weeks is the typical sweet-spot I see. I'm actually going to redo this video as I want to make a few changes, like what you suggest. Hopefully I can still get my point across in a very short video.
Oooooh nice. Kanban is actually not a "framework" like Scrum is...which is why Kanban works well with Scrum. Kanban does have cadences like retros and reviews...but not sprint based as you said...glad to see more and more ppl getting out of that "Versus" mindset!
Yeah, it's touchy on how exactly you describe it, as some people reject 'process', some reject 'methodology' and some reject 'framework.'
I just felt 'framework' was safe. Scrum definitely describes itself as a framework.
Thanks for the feedback!
In reality most Scrum teams don’t follow it slavishly, especially not if a critical bug shows up. Some flexibility is always needed, but I do like that Scrums gives some stability and it is nice when the team is able to come together at the start and the end of the sprint.
Very helpful. Thank you so much for sharing your knowledge. Have a great day. 🗓 👍249 likes
SCRUM MASTER!!!
sorry i got triggered