I make $0.00 on this TH-cam Channel. All I ask in return is a little flick on that LIKE button, and maybe SUBSCRIBE to the channel if you enjoyed the video. Thanks for your support 🙌
If we follow the agile approach then its dont allow to estimate in hours but when we are pulling down user stories from PBI to Sprint Planning, then how many user stories we have to pull? For eg: Team Capacity : 220 hours for 2 week sprint then how many user stories we can take in the sprint planning?
@@agilecoach My point is that, if we have capacity of 220hrs then how many user stories will cover in the First Sprint? and how we can say like that each user story will take x of hours or like that?
Hello Coach , For hours , we break down to sub tasks and estimate like average of min to max hours . But then if a slow person picks or if dependency or risks occurs , this the time estimated will not be met :) . Also we cant estimate on the waiting time for external or internal dependencies once its identified.. Answering clients , PO , and Management is always a problem in the Agile World..
I prefer to solve this problem by breaking the user story down into deliverables and using a range of hours to estimate each deliverable, a min-max. The reason is because clients push for a timeline. Clients also don't understand project size or story points as a measurement of how long they should expect to wait until their project is complete. If you provide a min-max for each task and them them up then you solve this problem.
In my organization, there is so much resistance from the project manager not to change to story points. Because he thinks he can manage it better by using day based estimates
Probably man/hour is better suited for estimating fine-grain sub-tasks. But a team may not even need to put an estimate for that. So T-shirts and Story Points remain the most versatile units for estimation.
could you create a video about how to convince stakeholders to estimate the story point instead of hours? Because as I know that many stakeholder always ask How long it will be done?
I make $0.00 on this TH-cam Channel. All I ask in return is a little flick on that LIKE button, and maybe SUBSCRIBE to the channel if you enjoyed the video.
Thanks for your support 🙌
i support you
i think this is your best video yet, insightful
Glad you liked the video Jack
If we follow the agile approach then its dont allow to estimate in hours but when we are pulling down user stories from PBI to Sprint Planning, then how many user stories we have to pull?
For eg: Team Capacity : 220 hours for 2 week sprint then how many user stories we can take in the sprint planning?
Do you estimate in story points? How many stories did you do on average per sprint? You can use this amount for the next sprint...
@@agilecoach My point is that, if we have capacity of 220hrs then how many user stories will cover in the First Sprint? and how we can say like that each user story will take x of hours or like that?
I suggest watching these videos:
th-cam.com/video/f3d-xADPxPM/w-d-xo.html
th-cam.com/video/BYGrg3Q8mjw/w-d-xo.html
Hello Coach , For hours , we break down to sub tasks and estimate like average of min to max hours . But then if a slow person picks or if dependency or risks occurs , this the time estimated will not be met :) . Also we cant estimate on the waiting time for external or internal dependencies once its identified.. Answering clients , PO , and Management is always a problem in the Agile World..
Thanks for sharing your experience. I suggest to also watch this video: th-cam.com/video/b_9zkKjgUEU/w-d-xo.html
when do you use story point is it means that you don't need track hours?
Why do you need to track hours?
the best agile channel
You are too kind
Grateful for your videos Coach !
Thanks a lot for watching Olivia
I prefer to solve this problem by breaking the user story down into deliverables and using a range of hours to estimate each deliverable, a min-max. The reason is because clients push for a timeline. Clients also don't understand project size or story points as a measurement of how long they should expect to wait until their project is complete. If you provide a min-max for each task and them them up then you solve this problem.
Great strategy
Superb ... Thanks 😊
Welcome 😊
Really good. But the management and the project managers still insist for day based estimates. How should we convince them to use story points?
I am afraid it is everywhere like that and moving to another company won't make any difference
You still provide delivery dates but your way of estimating is different. dont think that they really care about your estimation process..
In my organization, there is so much resistance from the project manager not to change to story points. Because he thinks he can manage it better by using day based estimates
Great. Does the project manager estimate work or the team? If it's the team, let them decide how they would like to estimate work
@agilecoach it is the team estimating. But the day estimations are never met. Surprise surprise.
Your content is relevant, latest, awesome 🙏👍 keep going sir
Thanks a lot for watching Ben
Probably man/hour is better suited for estimating fine-grain sub-tasks. But a team may not even need to put an estimate for that. So T-shirts and Story Points remain the most versatile units for estimation.
Good point Gasser
Hi coach
Could you do a video on what a SM should focus on first 30-90 days to their new/existing scrum team?
Watch this video and let me know if it helped th-cam.com/video/AeNdooem0XQ/w-d-xo.html
@@agilecoach thanks coach, That surely helps
Enjoyed the video coach
Glad you enjoyed
I would argue that an estimate is an informed guess at worst. Cone of Uncertainty and all that...
Great video coach
Glad you liked it!
could you create a video about how to convince stakeholders to estimate the story point instead of hours? Because as I know that many stakeholder always ask How long it will be done?
Great topic, will do
Make a video about SAFe please
Great idea, will do. Thanks for watching
Stakeholders must watch
True haha
i'm early today
Thanks for being early
liked
Thanks a lot