I would have added in the video that one of the most powerfull metric in Kanban with Scrum is to follow Item Aging Work In Progress during Daily Scrum. For me, it's a game changer to quickly identify item which is not going to respect the SLE. It helps the team to focus on and to find solution to get this item out of the system the best way possible. My team starts every single daily scrum with this chart. I would have added too that using Kanban and its flow metrics really help a Scrum team to be more predictable. You can follow your throughput, your cycle / lead time, define an SLE by using percentiles, running monte carlo simulation etc. Great video though. It's really hard to cover everything in 30 minutes or so.
Hi ! I don't totally agree on the "Changes to priorities" (around 20:16 ) regarding Scrum when you write that "sprint is fixed" : you should inspect the sprint backlog during the sprint and adapt it to reach the goal. It's the sprint goal that should not change, not the sprint backlog. So, if the new prioritary topic is related to the sprint goal, there is no problem to add it immediatly.
Love your videos. thanks so much for sharing and creating. Question in the Kanban example - Is it best to take from the top of the backlog as the highest priority item. In your case you chose a feature that appealed to you. Where does the priority of items come in?
In Kanban, the rules are set by the team. These aren't shown explicitly in the example. (Perhaps these are the top 5 items, all equally valuable, choosen from a much bigger set of ideas and requests.) But I would say yes, it makes total sense to order the top 5 so that you pull from the top :-)
WOW amazing video! Really learned a lot. Will test scrum with my team 😊
I would have added in the video that one of the most powerfull metric in Kanban with Scrum is to follow Item Aging Work In Progress during Daily Scrum. For me, it's a game changer to quickly identify item which is not going to respect the SLE. It helps the team to focus on and to find solution to get this item out of the system the best way possible. My team starts every single daily scrum with this chart.
I would have added too that using Kanban and its flow metrics really help a Scrum team to be more predictable. You can follow your throughput, your cycle / lead time, define an SLE by using percentiles, running monte carlo simulation etc.
Great video though. It's really hard to cover everything in 30 minutes or so.
Super great content, thank you a lot 👏🙏✨
Grymt Jimmy! Mycket bra sammanfattat.
Tack 🙏☺️
Hi !
I don't totally agree on the "Changes to priorities" (around 20:16 ) regarding Scrum when you write that "sprint is fixed" : you should inspect the sprint backlog during the sprint and adapt it to reach the goal. It's the sprint goal that should not change, not the sprint backlog.
So, if the new prioritary topic is related to the sprint goal, there is no problem to add it immediatly.
Love your visuals and the style!
Are they hand drawn? 😊
Also great content of course!
Thank you! And yes. All is drawn on my Samsung tablet :-)
Love your videos. thanks so much for sharing and creating. Question in the Kanban example - Is it best to take from the top of the backlog as the highest priority item. In your case you chose a feature that appealed to you. Where does the priority of items come in?
In Kanban, the rules are set by the team. These aren't shown explicitly in the example. (Perhaps these are the top 5 items, all equally valuable, choosen from a much bigger set of ideas and requests.)
But I would say yes, it makes total sense to order the top 5 so that you pull from the top :-)