Thank you for another great value video. You have given me a different perspective on estimation. I had actually paused on the estimation side of things but being educated by this video, I will certainly go back to doing the sprint backlog item estimation. The main takeaway was about the dynamics of value and effort in product refinement and perhaps equally if not more importantly, how estimation is about understanding the item better by discussing it in detail than the actual estimation itself. Hence and you gracefully put it - the means and not the end. If you don't mind answering this. In your two videos I have seen on estimation I would have loved a bit more details into the why of Fibonacci numbers rather than a linear scale. Many thanks!
Hey John! Thanks for explaining your takeaways from the video. It's really enriching for me to know what practical advice the viewers appreciate. About the estimation in Fibonacci numbers - it's about relativity. If you go with linear scale, you can't compare one item against another. With Fibonacci each next number is a sum of the two previous ones, so you can ask yourself the questions "is it bigger than the previous one? Is it smaller than the next one?" You can compare the stories against the ones previously estimated. I thought it is somehow explained in the other video "How to estime in story points?"
Hi Maria, thanks for your response. What you have explained in terms of the relativity of effort can still be coarsely achieved by a linear scale. Notwithstanding, after watching the second video again, I do see the nuanced distinction. Thank you once again. In this case, what would you say about using a linear scale and then rounding up to the Fibonacci scale?
@@JohnAlamina hey John, I though that would be overthinking it. In reality you can use any scale you like. Even cosmic points would be fine if the team knows what they mean ;-)
Love that comment - don’t sweat over the estimates but focus on delivering value. After all, that’s what we’re here to do! Gonna need to find out more about the noestimates movement. Looking forward to video 20. You’re doing a great job!
Thank you thank you thank you!!! You're videos are exactly what I needed to continue improving how I approach my job as an SM! Congratulations on reaching over 1K subscribers! I just reached 100 and I'm super stoked, lol. You're the best!
Hey Cindy, thank you! Glad to be of help 🥰Great to see you have a channel too, and about subject I'm interested in! You just got yourself a new subscriber! :)
Thank you for the great video...this addressed so many questions I had...I love the passion you have for your job. I work as a product owner in an IT company where one person in a scrum team does 50% dev work and 50% scrum master work. All IT companies I worked with perceive SM as a useless role in scrum, no wonder they don't understand scrum. And the SM with only 50% time and with their own dev targets don't care about training themselves or the team. Scrum guide too is brief on what a SM must do. Have you experienced this? It'd be helpful if you can make a video with examples/anecdotes of how SM contributes to the team and their job is more than just scheduling meetings.
Hey Sai, thank you so much for your comment. This is a common problem, I agree. I think it is better to share a SM even between 3 teams than share between the roles. Depends on a person, of course. I will think about your suggestion, this is fairly easy to demonstrate, something like "a day in life of a SM" :)
Can you please explain if the story points should be estimated after identifiying tasks for each story point or tasks have nothing to do with estimations ? Because against story points when you define tasks you realise how much efforts are required to implement a story
We used to first estimate the stories on the refinement and then break them out into tasks on the second part of planning. That's true that sometimes you might realize that but you estimate the complexity of the whole story and it's not about getting a perfect estimation, but rather an "estimation" to know how many stories you can pick for a Sprint considering your capacity :)
One of my favourite quotes from Jeff Patton's book about user story mapping: One thing that seems to be a secret, but really shouldn’t be, is that estimates are…estimated. Hit the Web and find any list of oxymorons. I’m confident you’ll find this term there: accurate estimate . If we knew exactly how long things would take, then we wouldn’t have called it an estimate , would we?
As a fellow agile coach, i can say you are clear and concise. you know your stuff. smart lady. i enjoy your videos :)
Thank you! 😊
Thank you for another great value video. You have given me a different perspective on estimation. I had actually paused on the estimation side of things but being educated by this video, I will certainly go back to doing the sprint backlog item estimation. The main takeaway was about the dynamics of value and effort in product refinement and perhaps equally if not more importantly, how estimation is about understanding the item better by discussing it in detail than the actual estimation itself. Hence and you gracefully put it - the means and not the end. If you don't mind answering this. In your two videos I have seen on estimation I would have loved a bit more details into the why of Fibonacci numbers rather than a linear scale. Many thanks!
Hey John! Thanks for explaining your takeaways from the video. It's really enriching for me to know what practical advice the viewers appreciate. About the estimation in Fibonacci numbers - it's about relativity. If you go with linear scale, you can't compare one item against another. With Fibonacci each next number is a sum of the two previous ones, so you can ask yourself the questions "is it bigger than the previous one? Is it smaller than the next one?" You can compare the stories against the ones previously estimated. I thought it is somehow explained in the other video "How to estime in story points?"
Hi Maria, thanks for your response. What you have explained in terms of the relativity of effort can still be coarsely achieved by a linear scale. Notwithstanding, after watching the second video again, I do see the nuanced distinction. Thank you once again. In this case, what would you say about using a linear scale and then rounding up to the Fibonacci scale?
@@JohnAlamina hey John, I though that would be overthinking it. In reality you can use any scale you like. Even cosmic points would be fine if the team knows what they mean ;-)
Love that comment - don’t sweat over the estimates but focus on delivering value. After all, that’s what we’re here to do! Gonna need to find out more about the noestimates movement. Looking forward to video 20. You’re doing a great job!
Thank you, Richard!
Thank you thank you thank you!!! You're videos are exactly what I needed to continue improving how I approach my job as an SM! Congratulations on reaching over 1K subscribers! I just reached 100 and I'm super stoked, lol. You're the best!
Hey Cindy, thank you! Glad to be of help 🥰Great to see you have a channel too, and about subject I'm interested in! You just got yourself a new subscriber! :)
Thank you for the great video...this addressed so many questions I had...I love the passion you have for your job.
I work as a product owner in an IT company where one person in a scrum team does 50% dev work and 50% scrum master work. All IT companies I worked with perceive SM as a useless role in scrum, no wonder they don't understand scrum. And the SM with only 50% time and with their own dev targets don't care about training themselves or the team. Scrum guide too is brief on what a SM must do. Have you experienced this? It'd be helpful if you can make a video with examples/anecdotes of how SM contributes to the team and their job is more than just scheduling meetings.
Hey Sai, thank you so much for your comment. This is a common problem, I agree. I think it is better to share a SM even between 3 teams than share between the roles. Depends on a person, of course.
I will think about your suggestion, this is fairly easy to demonstrate, something like "a day in life of a SM" :)
@@AgileStateofMind thank you 😊 I look forward to new content from you...wishing you the best!!
One of my favorite board-games Dixit on top shelf!
Indeed! :)
@@AgileStateofMind have you tried codenames? It Is great for team bonding as well :D
@@xandrosfavorites Oh yes, that is my second favourite to play on family events. Will need to try it with the teams! Thanks :)
@@AgileStateofMind Mysterium is another great spin on Dixit but it's a murder mystery :D
@@ThomasBanksDrBoon Sounds interesting, will check it out, thanks :)
Can you please explain if the story points should be estimated after identifiying tasks for each story point or tasks have nothing to do with estimations ? Because against story points when you define tasks you realise how much efforts are required to implement a story
We used to first estimate the stories on the refinement and then break them out into tasks on the second part of planning. That's true that sometimes you might realize that but you estimate the complexity of the whole story and it's not about getting a perfect estimation, but rather an "estimation" to know how many stories you can pick for a Sprint considering your capacity :)
One of my favourite quotes from Jeff Patton's book about user story mapping:
One thing that seems to be a secret, but really shouldn’t be, is that estimates are…estimated. Hit the Web and find any list of oxymorons. I’m confident you’ll find this term there: accurate estimate . If we knew exactly how long things would take, then we wouldn’t have called it an estimate , would we?
I love it that he calls it a "secret". We should make a prominent reveal of it :-)
@@AgileStateofMind his book is full of secrets ;D