This is the best explanation I have watched ever! I now know what all this story point stuff means. My team was pretty much guessing without me being able to really explain as the Scrum Master! LOL sad!
This is best Story Point Estimation Video .I would appreciate if we can have examples of Software Industry while explaining the risks,dependencies,value,complexity factors for story estimation.
Hi I have a very elementary question. In another video I saw that capacity planning was done in terms of hours ...so lets say output of capacity planning was xyz hours. Now estimation of stories are ABC storypoints. Now how do we decide that ABC storypoints can be accomodated in xyz hours? or We do not do such calculation ? for the sake of the above scenario, lets assume that it is first sprint and we do not have any velocity data available.
2:20 Story point estimation with business value? Hmmm that didn’t sounds right. Story point (sp) is from the viewpoint of the dev team. Business value (bv) is from the customers view. Both uses fibonacci sequence. Then compute them both to get the Priority Order = BV divided by SP then the result you sort in descending order. Just saying.
I would concur. Story point is more in terms of complexity, Business value is already being taken care of by PO by prioritizing the backlog for e.g. a story point with value 2 can be at top of the backlog.
Very nice explanatory video..I also need to understand what is the relationship between story point and capacity planning in hours if I want to allocate stories to team members
I joined a new project and the team is assigning SP values in this way. They take Dev estimates separately (say 5) and QA estimates separately (say 3). Now, they assign the story with 8 SP value. Similarly with other stories too, and thus come up with good number of velocity every sprint. Does it seem fine? How can it be corrected without impacting the velocity? Please help.
No this is not optimal, don't try to keep the velocity and try to improve the practice, it's like you can not change the speed of a car keeping the same values in speedometer
well explained. Clear and crisp. But still have a doubt how do we connect the size(story point) with effort(hrs)? For a story of medium complexity size if I get the size as 8, how do I take it further to required hours ? We generally do it based on historical data and knowledge of application functionality? Is there a specific way of doing that?
why don't you take a look at your velocity for that? If you estimated a task with 60 story points and your velocity in the last sprints was 30, that would mean you need 2 sprints to complete a task of this size
There is a story which requires minimal changes from Dev's end so they give 5 SP and the same story has to be tested on multiple screens so tester gives 13 SP. Which SP will be considered for the story 5 or 13 or the sum of both?
May be 5 , may be 13, may be none of them. The team needs re estimates, why there is just 5 and 13? Is it two Member team? In this case the Scrum Master must give a training to the team members about story points, from your example the team members don't understand what is story point. And how to estimate it
That was pretty good. How do you project a project schedule to a client during project planning phase? IT doesn't seem like Storypoint will get us there.
If the customer asks for end date before starting the project and it is required to decide on to give the project to seller or not . How the seller will calculate before starting any sprint
Hi, After listening to your video i have one basic question. Why we are opting for fibonacci series why can't we use 1,2,3,4,5,6 as story points number. What is so special on using fibonacci series ? Is it because this is used because it supports relative estimation? My understanding is correct
Thanks for the video. One thing I don't completely get: would that be a valid statement to say that XXS + XXS + XXS = S? I.e. does linear algebra work with the story points 1 + 1 + 1 = 3 and that's how we should relatively compare stories (approximately)?
Awesome video. Thank you so much for uploading. I am able to understand what actually the story points means and how it should be done. I request you to upload any video related how to manage conflicts between different teams when finalizing the story points for an user story. Thank You👍👌,👏
Hi! Thank you for very useful detailed video! I have a question and I'm not sure which of your videos I should look for an answer in. The question is: if we're using story points we shouldn't relate them anyhow to actual time, but how do we inform a client about the time (deadline) when we'll had him the result of our work? For the context - I'm trying to use Story Point Estimation in non software development sphere and there's need to inform a client about the date the job will be done. Thank you :)
This needs a culture and mindset shift, you need to understand how agile works what's their values and principles are? Once you follow them you will realize client is not only giving requirements and waiting for plan, timesheets deadlines, but also they are working together. It's little difficult for me to explain in this comment window.
How to handle such situation or scenario where team members are consistently estimating user stories not correctly. Let's take an example there are 1 user story which are simple can be done in 2-5 hrs but still team members are estimating it for say 2 days or so by saying buffer time in that we have experience members as well. How to approach as a SM also how to handle PO and other stakeholders in such case if it is consistently happening for few sprints.
when is the perfect time to do Sizing of PBI? I do it in backlog grooming session so that when we do the Sprint planning, the team must not waste much time on such activities and clearly start on what and how part.
@@AgileDigest Can we also do it in sprint planning? PO reads out the PBI and team sizes it using PP I have often observed and heard it doing the same during sprint planning.
I appreciate the orator's effort in sharing his knowledge. This is perfect example of why the communication skills are so important in every human being's life, that too if you are professional. If he would have written and given an explanation in a simple way, it would have been a lovely presentation. instead, if you are just telling whatever it is coming into your mind, it becomes so clumsy, and very hard to understand. In english there are couple of things you need to understand whenever you are making such sessions. One is grammar and the other one is having punctuation. if you are just reading it like a kid reading news paper without a comma or fullstop, its hard to understand. I amnt here to nail you down for your diction or accent, my suggestion will be have a better way of representing the session. Write it down in a notepad, correct your grammar, follow the punctuation & then present it. Hope my intention will be taken in a proper & positive sense.
#33 You have been asked to estimate the story points for a particular story using the Fibonacci sequence. You have reviewed the story, but it seems to indicate a significant amount of work and a number of unknowns, particularly around the creation of test data. At this point, you don’t know if you’ll be able to use existing data or will have to create your own. You also don’t know how you will test the interfaces between this story and the existing code. Given this information, what would be the proper value to assign in story points? a. 1 b. 5 c. 13 d. 18
Hi Aishwary, The Story Points estimation happens most of time during grooming ceremony. Team can estimate the story using planning poker. Remember Its not estimated by individual. The entire development team participates on estimating every story. Once the requirement for every story is clear to all, The estimate it using planning poker, and marked the story as groomed or defined. If there are any unknowns on the requirement, the story is parked for future grooming, once all the unknowns get clarified. During Sprint Planning Only Groomed stories are eligible to get committed. I suggest don't estimate a story with unknowns, and don't plan for any sprint. To keep you backlog healthy, work together with you PO, have all the clarification done. and then estimate it with a relative sizing. FYI : Your option d (18) is not a Fibonacci series number. To understand more about Grooming, Sprint Planning and Palling poker watch the video mentioned below 1. ua-cam.com/video/5j5iEekFwmI/v-deo.html (Grooming) 2. ua-cam.com/users/BSNLkg_8odQ (Planning Poker) 3. ua-cam.com/video/eGWre4YpUFQ/v-deo.html (Sprint Planning ) or visit agiledigest.com/
I am a bit unclear as why Business Value has been included as a parameter for story point estimation. I feel that the business value should only be used for back log prioritisation . I feel that if you do then only some high priority items will fill up the initial sprints and then it will give a incorrect sprint velocity
You are correct. business value should not be part of it. the video was created 4 years back. that time few organizations used to consider business value
It is purely bookish to suggest that while estimating in waterfall model there is very less chance to meet the estimate while doing so in Agile it is very less chance not to meet the estimate. In my opinion, probability of meeting them remains the same no matter which method you use for estimating it. The factors defining the probability to meet them are on the ground and not on the paper.or the spreadsheet where you do the estimates :-)
If one story carries 2 storypoint and another story is double the size why we not use 4 story points why 5..why fibonacci series used for story point estimation
We use Fibonacci, to maintain a consistent pattern of estimation, not accuracy. If you go with 1,2,3,4,5,6,7,8,9,... it will forced you to estimate precisely which can not be possible as estimate is always estimate.
How and who assigns a story point to the user story using Fibonacci Series. Say, I have 10 User Stories, who calls it as User story 1 as 3 story point, User story 2 as 8 story points.
Your mixing effort and value.. Its in my oppion a priority score you are estimating. Booth are important but the value part is the one influence how its should be ranked.. The story points are the effort including the risc complexity but NOT the value... Therefore when you then decide to prioritized you rank them according to most value for least effort
Thanks for nice video. I had one question...user story will be estimated using story points...how about the tasks of the user stories? Should we estimate hours for identified tasks?
the tasks under the user story are actionable item to generate the value of the parent user story. and can be estimated as hours of effort needed by the assignee of the specific task.
You literally became my "Agile Digest" to sharpen my skills. Keep sharing!
Thank You
@@AgileDigest àaaa0q
11111111111111111
11
@@AgileDigest 1111111
This is the best explanation I have watched ever! I now know what all this story point stuff means. My team was pretty much guessing without me being able to really explain as the Scrum Master! LOL sad!
Thank you Akilah.
Very nice video. Simple and effective explanation.
This is best Story Point Estimation Video .I would appreciate if we can have examples of Software Industry while explaining the risks,dependencies,value,complexity factors for story estimation.
Thanks so much for this video I learned a lot.
best explanation i came across for Story points. Thank you!
Great work!! Amazing video. This is very intuitive video. Thank you!!
very good video to understand story points and estimation. Thanks for sharing this.
Your tutorials are excellent!!!! Thank you so much.... highly appreciate your efforts!!! Best wishes!! 👍😇👏
Thank you very much for detailed explanation on story point estimation. It was helpful
You are most welcome
Great video. Thank you!! I understand estimation better and look forward to bringing my team along
Great video.. Very nicely explained.. I must say this is the best content I found on story point estimation..
Explained so well!!! Loved it and thank you 🤩
I went through some of yours agile video ...All the nicely explained ...Thanks
Excellent explanation-well done. 🙏
Simple and Excellent elaboration.
super examples!!! loved it
Thank you! 😃
Excellent video. Well explained on the concept of Story points.... Good work.
Thank you very much for such a detailed explanation. Liked and subscribed. Keep sharing informative tutorials like this.
Thank You Digant
Hi I have a very elementary question. In another video I saw that capacity planning was done in terms of hours ...so lets say output of capacity planning was xyz hours. Now estimation of stories are ABC storypoints. Now how do we decide that ABC storypoints can be accomodated in xyz hours?
or We do not do such calculation ?
for the sake of the above scenario, lets assume that it is first sprint and we do not have any velocity data available.
2:20 Story point estimation with business value? Hmmm that didn’t sounds right. Story point (sp) is from the viewpoint of the dev team. Business value (bv) is from the customers view. Both uses fibonacci sequence. Then compute them both to get the Priority Order = BV divided by SP then the result you sort in descending order. Just saying.
I would concur. Story point is more in terms of complexity, Business value is already being taken care of by PO by prioritizing the backlog for e.g. a story point with value 2 can be at top of the backlog.
I like so mcuh your trainig video because is very accurate and clarifying
You have excellent knowledge sir.
Excellent series and very well explained..thanks
Very nice explanatory video..I also need to understand what is the relationship between story point and capacity planning in hours if I want to allocate stories to team members
Good explanation with respect to the relative sizing of story points
now i understand better !! thank you
Very nice explanation and example used are awesome.. cheers..
Good video, covered some really good topics. Thank you!
Great work amazing video.
Thank you very much!
I liked your examples...
Very useful many thanks
Niladri nailed !!!! Awesome analysis !!!
Excellent video. Well explained.
Great video! Thanks !!
Nice n organised tutorial. Thanks
Well arranged and presented.
Nice explanation thanks
very informative video
I joined a new project and the team is assigning SP values in this way. They take Dev estimates separately (say 5) and QA estimates separately (say 3). Now, they assign the story with 8 SP value. Similarly with other stories too, and thus come up with good number of velocity every sprint. Does it seem fine? How can it be corrected without impacting the velocity? Please help.
No this is not optimal, don't try to keep the velocity and try to improve the practice, it's like you can not change the speed of a car keeping the same values in speedometer
well explained. Clear and crisp. But still have a doubt how do we connect the size(story point) with effort(hrs)? For a story of medium complexity size if I get the size as 8, how do I take it further to required hours ? We generally do it based on historical data and knowledge of application functionality? Is there a specific way of doing that?
why don't you take a look at your velocity for that? If you estimated a task with 60 story points and your velocity in the last sprints was 30, that would mean you need 2 sprints to complete a task of this size
There is a story which requires minimal changes from Dev's end so they give 5 SP and the same story has to be tested on multiple screens so tester gives 13 SP. Which SP will be considered for the story 5 or 13 or the sum of both?
May be 5 , may be 13, may be none of them. The team needs re estimates, why there is just 5 and 13? Is it two Member team? In this case the Scrum Master must give a training to the team members about story points, from your example the team members don't understand what is story point. And how to estimate it
That was pretty good. How do you project a project schedule to a client during project planning phase? IT doesn't seem like Storypoint will get us there.
good video. can you do a video on aligning metrics to the story points?
Great suggestion!
How can i see your interview video
Interview video are not yet public, those are available for Participants of ESM class only
Super Video
If the customer asks for end date before starting the project and it is required to decide on to give the project to seller or not . How the seller will calculate before starting any sprint
Thanks for the info, Story points work´s with kanban also?
Not needed
Hi, After listening to your video i have one basic question. Why we are opting for fibonacci series why can't we use 1,2,3,4,5,6 as story points number. What is so special on using fibonacci series ? Is it because this is used because it supports relative estimation? My understanding is correct
Please share link of one authenticated article which talks about business value as a factor used to calculate story points?
How would i know 15 story points will fit in a 2 week sprint ? There is no connection created between story points and amount of days.
There is no relationship between story points and amount of days or hours
Very meticulously created videos. Thank you! Out of curiosity ,what tool are you using to create these videos?
Thanks for the video. One thing I don't completely get: would that be a valid statement to say that XXS + XXS + XXS = S? I.e. does linear algebra work with the story points 1 + 1 + 1 = 3 and that's how we should relatively compare stories (approximately)?
Thank You
That's a very comprehensive answer to the question ;)
Awesome video. Thank you so much for uploading. I am able to understand what actually the story points means and how it should be done. I request you to upload any video related how to manage conflicts between different teams when finalizing the story points for an user story. Thank You👍👌,👏
Hi! Thank you for very useful detailed video! I have a question and I'm not sure which of your videos I should look for an answer in. The question is: if we're using story points we shouldn't relate them anyhow to actual time, but how do we inform a client about the time (deadline) when we'll had him the result of our work?
For the context - I'm trying to use Story Point Estimation in non software development sphere and there's need to inform a client about the date the job will be done.
Thank you :)
This needs a culture and mindset shift, you need to understand how agile works what's their values and principles are? Once you follow them you will realize client is not only giving requirements and waiting for plan, timesheets deadlines, but also they are working together. It's little difficult for me to explain in this comment window.
@@AgileDigest thank you for super quick reply! I'll think about your words and will try to dive deeper in Agile principles then :)
hi All, when we estimated the user stories in story points, but when we go to sprint we estimate in hours...why is that so ?
Don’t ever estimate in hours. That defeats the purpose of agile estimation.
How we can define the project estimation
Roll up stories to feature, and feature to epic. Or use separated epic points
Thank you very much!
thanks
How to handle such situation or scenario where team members are consistently estimating user stories not correctly. Let's take an example there are 1 user story which are simple can be done in 2-5 hrs but still team members are estimating it for say 2 days or so by saying buffer time in that we have experience members as well. How to approach as a SM also how to handle PO and other stakeholders in such case if it is consistently happening for few sprints.
Excellent information. Thanks a lot. After ranking the story points , do we to sum the rankings of all the story points to arrive at the Project size?
No need
when is the perfect time to do Sizing of PBI? I do it in backlog grooming session so that when we do the Sprint planning, the team must not waste much time on such activities and clearly start on what and how part.
That's perfect. That's the best time.
@@AgileDigest Can we also do it in sprint planning? PO reads out the PBI and team sizes it using PP I have often observed and heard it doing the same during sprint planning.
@@kishores1020 Yes you can.
How story point estimation helps ,? Till now I m not able to understand why story points needs to be assigned
I appreciate the orator's effort in sharing his knowledge. This is perfect example of why the communication skills are so important in every human being's life, that too if you are professional. If he would have written and given an explanation in a simple way, it would have been a lovely presentation. instead, if you are just telling whatever it is coming into your mind, it becomes so clumsy, and very hard to understand. In english there are couple of things you need to understand whenever you are making such sessions. One is grammar and the other one is having punctuation. if you are just reading it like a kid reading news paper without a comma or fullstop, its hard to understand. I amnt here to nail you down for your diction or accent, my suggestion will be have a better way of representing the session. Write it down in a notepad, correct your grammar, follow the punctuation & then present it. Hope my intention will be taken in a proper & positive sense.
#33 You have been asked to estimate the story points for a particular story using the Fibonacci
sequence. You have reviewed the story, but it seems to indicate a significant amount of work and
a number of unknowns, particularly around the creation of test data. At this point, you don’t know
if you’ll be able to use existing data or will have to create your own. You also don’t know how you
will test the interfaces between this story and the existing code.
Given this information, what would be the proper value to assign in story points?
a. 1
b. 5
c. 13
d. 18
Hi Aishwary,
The Story Points estimation happens most of time during grooming ceremony. Team can estimate the story using planning poker.
Remember Its not estimated by individual. The entire development team participates on estimating every story.
Once the requirement for every story is clear to all, The estimate it using planning poker, and marked the story as groomed or defined. If there are any unknowns on the requirement, the story is parked for future grooming, once all the unknowns get clarified.
During Sprint Planning Only Groomed stories are eligible to get committed.
I suggest don't estimate a story with unknowns, and don't plan for any sprint. To keep you backlog healthy, work together with you PO, have all the clarification done. and then estimate it with a relative sizing.
FYI : Your option d (18) is not a Fibonacci series number.
To understand more about Grooming, Sprint Planning and Palling poker watch the video mentioned below
1. ua-cam.com/video/5j5iEekFwmI/v-deo.html (Grooming)
2. ua-cam.com/users/BSNLkg_8odQ (Planning Poker)
3. ua-cam.com/video/eGWre4YpUFQ/v-deo.html (Sprint Planning )
or visit agiledigest.com/
I am a bit unclear as why Business Value has been included as a parameter for story point estimation. I feel that the business value should only be used for back log prioritisation . I feel that if you do then only some high priority items will fill up the initial sprints and then it will give a incorrect sprint velocity
You are correct. business value should not be part of it. the video was created 4 years back. that time few organizations used to consider business value
It is purely bookish to suggest that while estimating in waterfall model there is very less chance to meet the estimate while doing so in Agile it is very less chance not to meet the estimate. In my opinion, probability of meeting them remains the same no matter which method you use for estimating it. The factors defining the probability to meet them are on the ground and not on the paper.or the spreadsheet where you do the estimates :-)
This is true if the requirement are clear however in most waterfall project requirements are not clear.
If one story carries 2 storypoint and another story is double the size why we not use 4 story points why 5..why fibonacci series used for story point estimation
We use Fibonacci, to maintain a consistent pattern of estimation, not accuracy. If you go with 1,2,3,4,5,6,7,8,9,... it will forced you to estimate precisely which can not be possible as estimate is always estimate.
How and who assigns a story point to the user story using Fibonacci Series. Say, I have 10 User Stories, who calls it as User story 1 as 3 story point, User story 2 as 8 story points.
+Mobs , please watch the video on backlog grooming, i have explained planning poker . It will clarify your doubt.
+Mobs and also watch the video on understanding planning poker.
The team chooses the point value after discussion. They agree on it.
Your mixing effort and value.. Its in my oppion a priority score you are estimating. Booth are important but the value part is the one influence how its should be ranked.. The story points are the effort including the risc complexity but NOT the value...
Therefore when you then decide to prioritized you rank them according to most value for least effort
Hi can you explain, When to do the T-Shirt estimation and when to do the Fibonacci estimation?
You can use either of them, using Story points have the benefits to calculate with numbers for certain metrics and KPI.
what is answer for story point , can you please explain ?
it will help you to define the velocity of the team. Once the team will adapt it then in future anyone can do the planning to sprint.
If u have practical examples let us share
Thanks for nice video. I had one question...user story will be estimated using story points...how about the tasks of the user stories? Should we estimate hours for identified tasks?
the tasks under the user story are actionable item to generate the value of the parent user story. and can be estimated as hours of effort needed by the assignee of the specific task.
@@AgileDigest thank you. What is the good practice for task estimation? Is there any suggestion for duration of tasks?
@@Makeovertime. Its ideally should be estimated by the team member who will be executing the task
Hi, it's a great video but the background music is too loud & annoying. Please remove it if possible. Thanks
he is not saying how story points is converted into task and hours
U r not explaining why story points are required
Even layman can also understand
Thank you
@Agile Digest, could you please make a video on Real time scrum master interview questions and answers. thanks in advance
Sure, will make some soon, you can also explore our path to become scrum master course
If user story needs estimation in hrs why ahai points and make people mad
Story dont need Hours estimation, SubTask or Child of story (Task) does
Everything is described in another video.waste of 30min
Which is the another video? And why did you spent 30 min if it was same ?