yes , in Scrumban we don't commit to certain scope , but we commit to some KPI's or Service Level Expectations , WIP's , Lead time etc. otherwise it is too free and loose process , like: customers order something and we say to them we ll see when we deliver it to you. that would nt be delivering value. Another thing that I miss is paying attention to complexity as a factor in choosing the right framework. Kanban is more suitable for developing simpel products , and Scrum or Scrumban is more suitable for complex products.
Hi,many thanks for valuable video series. Your explanation is very lean and understandable. I want to implement scrumban methods for supply chain and purchasing processes. But I don’t sure management with compatibility. If you have a best practice example,I would have success by your sharing. Best Regards
Hi Anca, what methodology would you recommend for a data science team where team member works for different analysis which do not form a unitar product in the end and each analysis has a different stakeholder? I was thinking to try scrumban in 3 weeks sprints because based on team feedback 2 w were to tight comparing with the tooling and complexity of the tasks. Thanks a lot. Mike
Thanks for the video :) we are implementing Scrumban un our team and I'm trying to figure out how to make KPIs work with story points. Do you recommend using story points in Scrumban? Or rather time estimations?
That is not true. Scrumban is a way to work on its own. You may use Scrumban till eternity without going 100% over to Kanban (or Scrum). But it can be used as a transition, but that is just an option.
![[Live สด] การออกรางวัลสลากกินแบ่งรัฐบาล งวดวันที่ 16 พฤศจิกายน 2567](http://i.ytimg.com/vi/wPd7VFfWHIA/mqdefault.jpg)
yes , in Scrumban we don't commit to certain scope , but we commit to some KPI's or Service Level Expectations , WIP's , Lead time etc. otherwise it is too free and loose process , like: customers order something and we say to them we ll see when we deliver it to you. that would nt be delivering value.
Another thing that I miss is paying attention to complexity as a factor in choosing the right framework. Kanban is more suitable for developing simpel products , and Scrum or Scrumban is more suitable for complex products.
Thank you so much for sharing your knowledge. It is a very clear video, you get directly to the point.
I’m glad to hear that! Any questions, or video suggestions are welcomed.
thanks a lot the video is very useful
Hi,many thanks for valuable video series.
Your explanation is very lean and understandable.
I want to implement scrumban methods for supply chain and purchasing processes.
But I don’t sure management with compatibility.
If you have a best practice example,I would have success by your sharing.
Best Regards
Which of the 3 is best for Production support?
Hi Anca, what methodology would you recommend for a data science team where team member works for different analysis which do not form a unitar product in the end and each analysis has a different stakeholder? I was thinking to try scrumban in 3 weeks sprints because based on team feedback 2 w were to tight comparing with the tooling and complexity of the tasks. Thanks a lot. Mike
Thanks for the video :) we are implementing Scrumban un our team and I'm trying to figure out how to make KPIs work with story points. Do you recommend using story points in Scrumban? Or rather time estimations?
Scrumban is about transitioning from scrum to kanban, its not a methodology in its own right
That is not true. Scrumban is a way to work on its own. You may use Scrumban till eternity without going 100% over to Kanban (or Scrum). But it can be used as a transition, but that is just an option.