Комментарии:
Thank you! I have been trying to explain this to my new team and you are very thorough. I will be sharing this with them.
ОтветитьI didn't like it , 99% of the estimates is defined by managers , developers just follow
ОтветитьAwesome explanation Vibhor. I have a question. Some teams calculating Dev estimate , Test estimate separately and summing those to get final story point instead of following relative estimate technique. E.g. if dev gives 3sp, tester gives 2Sp the overall estimate is given as 5sp where as actually this is a 3SP user story based on the reference story.
Also, is calculating individual velocity a right approach or an anti pattern? - Kindly throw some light on these questions.
very useful videos, thanks Vibhor
ОтветитьGreat. Thanks for showing a way to find references for different story points for other domains like systems engineering.
ОтветитьI have a question about the user story references technique.
Why you need first compute the total value (Complexity+Risk+Effort) for each user story selected then sorting, then, assign a Fibonacci value to finally have the final user story size?
What happend if assign the Fibonacci values from the beginning to my selected user stories, without the previous classification?
Did you explain this in another video?
Anyway thanks for this fantastic video about user story estimation
Should we estimate bugs?
ОтветитьWhat if : "The product master hands over the results of sprint 1 to the customer, the customer accepts the results of this sprint. Then , while working on sprint 2 , customer wants to add some functionality related to sprint 1" , how do we handle Estimate User Stories ?
Ответитьawesome content , will keep watching
ОтветитьHi Vibhor!
Thanks for you video!
Evaluation in SP or hours has its pros and cons, and in principle it is possible to justify the choice of any of them.
You said that converting SP to hours is a mistake, ok))
But what do you say to such a question: let's say you chose an estimate in SP; the team evaluated "effort"for this task = 5 SP.
we konow, that for billing purposes, all developers track the time in hours. After completing the task, we see 25 hours in this task.
How to assess whether the team got into the estimation or not for this particular task?
Bottle neck is that we have an estimate in SP, but the time tracking is in hours.
Excellent
ОтветитьThank you Vibhor, great explanation! 🙏
ОтветитьIf there are no estimates, how do we know when the resources will be available to work on another project?
ОтветитьLove the way agile being explained
ОтветитьGood content, keep it up ! But how do you think the team will be aligned and pick 5 US from 100 (for example)? for that you should review all the US?
ОтветитьMany thanks for your videos. Always well detailed and easy to follow. Differnce between Acceptance Criteria and Definition of Done, well explained. Thumbs up!
ОтветитьLittle different to make story map..is any other alternative way to setup storymap
ОтветитьI love the way you break things down, been watching a couple of your videos and it’s very comprehensive sir 👌 thank you 🙏🏽
ОтветитьHi Vibhor, thanks for the awesome explanation! I have been enjoying n leaning a lot from your videos. I have one request, If you could slow down pace of your speech a bit..it would give more time to listeners to absorb and understand the whole thing more easily as there is so much to pick from each video.
ОтветитьYou are awesome as always. Thank you.
Isn’t it ideal to mature to a state of small slices of user stories and go with no of user stories to be delivered in a sprint as estimate than going with story points?
I know practically it isnt easy to achieve however going with user story count for forecasts sound simple. What do you think?
With no-estimate - how to get the release dates for the project? How to forecast ?
Ответитьnice and informative video
ОтветитьHow could the swimlane technique be done virtually?
ОтветитьWhat is the logic behind using fibonacci series . why only fibonacci . i had used personally fibonacci in technical analysis of trading shares in share market .
ОтветитьWhat is the difference between efforts and estimate?
ОтветитьExcellent explanation, so helpful, thank you! A follow up question: how often is this process done? Is this a process repeated each time new stories are added to the product backlog? I’m a bit confused how this element fits into the Agile iterations/sprints. Thank you.
ОтветитьFeedback - new subscriber
ОтветитьI daily go through your videos please can you explain user stories in detail, with int var char charcters with sql
ОтветитьTanks handsome .
ОтветитьHi Vibhor,
Can we decide reference stories on the basis of stories completed in the previous sprints? Actually, we decide our reference stories every quarter.
Thanks your videos are exceptionally well detailed.
I will be looking forward hearing from you.
Hi Vibhor, your videos are really helpfull, thank you so much. I have a question though. Do you have a workflow of your own to work with the stakeholers, sme's and scrumteam such as lean inception?
ОтветитьIt was very detail video with practical tips. Thanks.
Ответитьvery well explained on story map
ОтветитьHey Vibhor. I really like your videos. I am new to the field of Scrum Master. Your Videos do help me. Please keep on bringing new videos on new concepts. Is this the place to ask you if I need help in my work or can we contact you via mail too.
ОтветитьFeedback- You gained one more subscriber 😊
ОтветитьWould you have any guidance to implement scrumban?
Ответить... or Am he?
ОтветитьI love your videos man!
ОтветитьGreat one! Thanks
ОтветитьI didn't know that Jeff Goldblum was from India! ;-)
Ответить😍 Crushing… thank you
ОтветитьGreat video!!
ОтветитьHi Vibhor...I disagree on one point..the mistake 4...the ref. Baseline for a story will not change
It will change Vibhor. As the team gains experience, a 5 Storypointer could become a 3 Storypointer bcoz. There are now APIs which are reusable, and I have automated testing and my team also improved technically.
Let me know ur thoughts
Great info Vibhor...thq!!
ОтветитьShould we estimate defects, improvement stories and tasks? Again " it all depends" is not what I'm looking for, but in general and in agile world is it a good practice to estimate?
Ответить