@@taitsmith8521 And you cared so little about it, you bothered to comment above. So, there's that. But you obviously missed the sarcasm intended specially for you 🤡
Hi, watch this video ruclips.net/video/hQOs5CfkOJU/видео.html and then this one ruclips.net/video/k22ZwODjgkE/видео.html and that should answer your question..
The metrics presented in this video are metrics of the Lean approach. The Lean approach and Scrum diverge on some aspects, such as flow versus sprints. In my understanding, it is not really Scrum you are talking about.
Hi and thanks for the comment. I would certainly beg to differ and so would the Scrum Guide. Extract from the Scrum Guide, ‘Scrum is founded on empiricism and lean thinking. Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. Lean thinking reduces waste and focuses on the essentials’. What I’m describing in this video is perfectly applicable to Scrum and is complementary. What Scrum specific ‘metrics’ are you thinking of? The concept of Flow works perfectly well with sprints in Scrum and I would argue is not just beneficial but necessary.
@@TheAgileLeanGardener There are Scrum and Kanban, different approaches, different use cases. Then people invented ScrumBan, a kind of hybrid approach. Scrum specific metrics are velocity , burndown, story points. But we all know here that you don't like them. Kanban metrics are WIP, Lead Time, Cycle Time.
Well, as I'm sure you know, Story Points have nothing to do with Scrum, they are throw back to XP and even the guy who invented them (Ron Jeffries) apologised for creating them back in 2019. There is not a single mention of Story Points or Velocity in any of the Scrum Guide versions, not one. But Lean is mentioned several times. The Scrum metrics you're talking about simply have nothing to do with Scrum and never have - they've been used by teams because they 'heard' that's what they're meant to be using not because they are 'Scrum' metrics because they clearly are not. The measures I'm talking about will actually help teams, Scrum teams, to understand their delivery in a better way as well as causing the right conversations to happen leading to better outcomes. Genuinely I am not having a go but when people think/assume Story Points, Velocity etc are part of Scrum (when they never have been) it rubs me up the wrong way because I've seen over may years the pointlessness of them. I am a strong advocate of no estimates - but no estimates does not mean we don't discuss the work, break it down and discover dependencies, of course we need to do this.
@@TheAgileLeanGardener Scrum guide mentions estimates. And story points are (or were) the de facto standard to estimate user stories. Note that user story is not a Scrum idea neither. Story points (estimates) serve the same purpose for Scrum than WIP does for Kanban.
No, it doesn't mention estimates. It mentions forecasts. Perhaps give it another read ;-) and the best way to forecast is to use Monte Carlo Simulation. Since when is the de facto way to estimate to use story points?! In my experience using story points is a terrible way to 'estimate' (and we shouldn't be estimating anyway as it is a waste of time - yes, discuss the work, break it down but don't put a meaningless number on it - use a data driven approach based on reality). Yes exactly user stories are also not part of Scrum just as story points are not.
The first mistake is using Scrum. Every certified Scrum master I've ever encountered insists on points, velocity, burn down charts, etc, etc. All of it is waste.
I would disagree with that. A Scrum Masters main goal should be to help the team every day to deliver value to their customers. Part of which could be to ‘help’ the team remove impediments themselves not to spoon feed them by running around like a glorified dogs body. Removing impediments at the organisation level is a worthy cause and something the Scrum Master should be doing. People often jump on the ‘removing impediments’ and think this is what a Scrum Master should be doing but there is a lot more to it than that which is what I’ve tried to highlight in this video.
This is the best 'what does a scrum master do all day' video I've seen yet, great job! 👍
Thank you, I really appreciate that 🙏👍
I really like your data led approach, will definitely start tracking cycle time and try forecasting with Monte Carlo
Cool 😎 let me know how it goes
@@TheAgileLeanGardener sure and thank you for all your help!!
You’re very welcome 🤗
I've recently found the agile gardener. Great videos, thanks for sharing your knowledge 🎉
Thank you, I really appreciate that, means a lot 🙏👍
What a great video. I have never heard of Montecarlo before. WEhere can I find more information about it? Thank you
Thank you so much I really appreciate that 🙏👍 you can find more information on Monte Carlo here ruclips.net/video/hQOs5CfkOJU/видео.html
I like the way you add an element of fun into your videos, makes them a lot more watchable 🙂
Thanks 🙏 I appreciate that, I try my best :-)
Another great vid, will def check out Monte Carlo
Yep give it a go, it’s easy to do, let me know if you need any help 👍
This is such an awesome video!
Thank you so much I really appreciate that 🙏
.Thanks for sharing your knowledge.
Thank you 🙏👍
I lost patience. I don't care to find out what scrum is.
🤣
Then you aren't ready to be one ahahahahahahah
I just Googled "scrum master" inside a minute. Basically a project leader, severely overpaid after 7+ year's experience.
@@barrymitchell6444 Yeah, the thing is.......the thing is that I quit caring roughly 12 days ago...
So, there's that.
🤭
@@taitsmith8521 And you cared so little about it, you bothered to comment above. So, there's that. But you obviously missed the sarcasm intended specially for you 🤡
Great vid!
Thanks 🙏
A great video
Thank you 🙏👍😊
Great 👍🏻👍🏻👍🏻
Thanks 🙏 glad you enjoyed it 👍
How to calculate the 85%?
Hi, watch this video ruclips.net/video/hQOs5CfkOJU/видео.html and then this one ruclips.net/video/k22ZwODjgkE/видео.html and that should answer your question..
The metrics presented in this video are metrics of the Lean approach. The Lean approach and Scrum diverge on some aspects, such as flow versus sprints. In my understanding, it is not really Scrum you are talking about.
Hi and thanks for the comment. I would certainly beg to differ and so would the Scrum Guide. Extract from the Scrum Guide, ‘Scrum is founded on empiricism and lean thinking. Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. Lean thinking reduces waste and focuses on the essentials’. What I’m describing in this video is perfectly applicable to Scrum and is complementary. What Scrum specific ‘metrics’ are you thinking of? The concept of Flow works perfectly well with sprints in Scrum and I would argue is not just beneficial but necessary.
@@TheAgileLeanGardener There are Scrum and Kanban, different approaches, different use cases. Then people invented ScrumBan, a kind of hybrid approach.
Scrum specific metrics are velocity , burndown, story points. But we all know here that you don't like them.
Kanban metrics are WIP, Lead Time, Cycle Time.
Well, as I'm sure you know, Story Points have nothing to do with Scrum, they are throw back to XP and even the guy who invented them (Ron Jeffries) apologised for creating them back in 2019. There is not a single mention of Story Points or Velocity in any of the Scrum Guide versions, not one. But Lean is mentioned several times. The Scrum metrics you're talking about simply have nothing to do with Scrum and never have - they've been used by teams because they 'heard' that's what they're meant to be using not because they are 'Scrum' metrics because they clearly are not. The measures I'm talking about will actually help teams, Scrum teams, to understand their delivery in a better way as well as causing the right conversations to happen leading to better outcomes. Genuinely I am not having a go but when people think/assume Story Points, Velocity etc are part of Scrum (when they never have been) it rubs me up the wrong way because I've seen over may years the pointlessness of them. I am a strong advocate of no estimates - but no estimates does not mean we don't discuss the work, break it down and discover dependencies, of course we need to do this.
@@TheAgileLeanGardener Scrum guide mentions estimates. And story points are (or were) the de facto standard to estimate user stories. Note that user story is not a Scrum idea neither. Story points (estimates) serve the same purpose for Scrum than WIP does for Kanban.
No, it doesn't mention estimates. It mentions forecasts. Perhaps give it another read ;-) and the best way to forecast is to use Monte Carlo Simulation. Since when is the de facto way to estimate to use story points?! In my experience using story points is a terrible way to 'estimate' (and we shouldn't be estimating anyway as it is a waste of time - yes, discuss the work, break it down but don't put a meaningless number on it - use a data driven approach based on reality). Yes exactly user stories are also not part of Scrum just as story points are not.
Pls avoid background music in all videos.
Is it distracting? I like it personally but maybe I have it set too loud I’ll reduce the volume in future.
The first mistake is using Scrum. Every certified Scrum master I've ever encountered insists on points, velocity, burn down charts, etc, etc. All of it is waste.
😂
@@TheAgileLeanGardener I was laughing and confused
Scrum master main goal is remove impediments.
I would disagree with that. A Scrum Masters main goal should be to help the team every day to deliver value to their customers. Part of which could be to ‘help’ the team remove impediments themselves not to spoon feed them by running around like a glorified dogs body. Removing impediments at the organisation level is a worthy cause and something the Scrum Master should be doing. People often jump on the ‘removing impediments’ and think this is what a Scrum Master should be doing but there is a lot more to it than that which is what I’ve tried to highlight in this video.