Is this what you provide to new teams who aren't using relative estimation? What if the developers are already taking into consideration risk and complexity into their time estimate (ex: initially estimated it at 2 days, then with risk and complexity estimated it at 4 days) how would you present the benefit of relative estimation?
I will first present to my team why estimating in time is not working. As a team, are we estimating PBI for 4 days and way off with our estimate (eg: 6 days or more)? Is the developers all participating in estimation ( in my experience when we’re estimating in days, the developer that is doing the work usually give the days that will take them to do the work, which eliminate the team collaboration and conversation), how about spill overs? Are we able to accomplish our sprint goal? Are we able to deliver PSI? If not, I will suggest trying relative estimation which will encourage team focusing on the effort, complexity, and risk of doing the PBI (regardless of the days). Also with relative estimation at the end of 5 sprint we can get the team average velocity, which we can use as baseline on how many PBI we can commit to for upcoming sprints. we are unable to do this when estimating in hours/days. Benefit of Relative Estimate: Team collaboration, raise concerns with PBI through detail conversation, team participating in voting based on their understanding of the task, ask clarifying questions, and also give realistic expectations on Releases based on the team average velocity.
Is this what you provide to new teams who aren't using relative estimation? What if the developers are already taking into consideration risk and complexity into their time estimate (ex: initially estimated it at 2 days, then with risk and complexity estimated it at 4 days) how would you present the benefit of relative estimation?
I will first present to my team why estimating in time is not working. As a team, are we estimating PBI for 4 days and way off with our estimate (eg: 6 days or more)? Is the developers all participating in estimation ( in my experience when we’re estimating in days, the developer that is doing the work usually give the days that will take them to do the work, which eliminate the team collaboration and conversation), how about spill overs? Are we able to accomplish our sprint goal? Are we able to deliver PSI?
If not, I will suggest trying relative estimation which will encourage team focusing on the effort, complexity, and risk of doing the PBI (regardless of the days). Also with relative estimation at the end of 5 sprint we can get the team average velocity, which we can use as baseline on how many PBI we can commit to for upcoming sprints. we are unable to do this when estimating in hours/days.
Benefit of Relative Estimate: Team collaboration, raise concerns with PBI through detail conversation, team participating in voting based on their understanding of the task, ask clarifying questions, and also give realistic expectations on Releases based on the team average velocity.
Thanks for the clarity!
WOW!! Great video Aisha. Thanks for all the effort you put to provide and share yor knowledge. BIG THANKS!!
Thank you 🙏🏾
Wow! The time and effort you applied is really reflected in this content rich video. This video is extremely valuable. Well done!
Thank you 🙏🏾
wow great video you deserve 1,000,000 subscribers
As in,she's very vast.she knows this thing called agile
Thank you 🙏🏾 🙏🏾🙏🏾
Awesome; perfect content. Thank you so much. You nailed it💪🏾. I paused and subscribed after the first few minutes of listening.
Thank you 🙏🏾, I appreciate it
Does these story points include the efforts of both development and testing?
Yes it is 🙏🏾🙏🏾🙏🏾
Thank you so much for all your videos. Can you do a video on Dependencies and Technical debt. Thank you!
Sure I will 🙏🏾🙏🏾
I thoroughly enjoyed this lesson, thank you Aisha.
Thank you for watching 🙏🏾🙏🏾🙏🏾
I just finished watch the whole video
It was helpful
Thanks coach
Thank you 🙏🏾
I have watched this more than 5 times
More Grace Coach
Thank you 🙏🏾
Great video. I need to connect with you. Thank you very much
Thank you. You can email me at jallohaisha1@gmail.com
Round of applause. very well explained!
Thank you 🙏🏾
This video is Gold !!!🥇 Thanks
Thank you Mavis 🙏🏾🙏🏾🙏🏾
thanks doe this videos!
Thank you for watching 🙏🏾🙏🏾🙏🏾
Wow great 👍 hands-on.
Thank you 🙏🏾