September 28 & 29, 2020 | Virtual
Please login or join to subscribe to this thread
In fact, I find Kanban complements Scrum in a very good way. Check the Scrum with Kanban guide by Scrum.org
@Rami, many thanks.
Unless there is a comment that I can’t see then It’s Rami, not Kiron. I haven’t changed my name yet :-)
There is a big mistake in the use of things like Scrumban. My recommendation is to avoid it. Why? Scrum is one and only one at it is stated inside the Scrum Guide. Scrum is a framework and this is the power because you can fill it up in the way best fit for you current situation. There is no line inside Scrum about you have to use things like user stories, story points, kanban boards, etc. On the other side, Kanban is a full system where system is not a software system. With all this into account fill Scrum in the way best fit for creating the solution. About Kanban, if you are working inside a manufacturing company, go to the factory and I am pretty sure you will see Kanban in action.
Scrumban is NOT a single method or approach. Rather it is an attempt to leverage good practices from both taking into account the context of your team or need.
Ajay Reddy's book on Scrumban is worth reading - you may not decide to adopt it fully, but there might be ideas within it which are worth incorporating.
@Sergio, I have heard of Scrumban being used as path or transition phase while changing from Scrum to Kanban. Though it sounds like you are suggesting it should be either Scrum or Kanban, and that a transition phase is not necessary.
@Kiron, I've certainly heard of Scrumban also being used to leverage good practices from both Scrum and Kanban. I suppose it would depend on the industry where this might work well.
@Sergio, I hear you on that. They are buzzwords, indeed.
Please login or join to reply