In my previous article, we have discussed User Story in Agile Scrum. In this article, we will learn what Story Point is and what Story Point Estimation techniques are.
Story Point in Agile Scrum
A Story Point is a unit of measurement of the overall effort needed to complete specific requirements of a product backlog item. When we have our product backlog ready and when a team is ready for next sprint, they pull the priority user stories from the product backlog and start estimation for completing the user stories.
Story Point in Agile Scrum
A Story Point is a unit of measurement of the overall effort needed to complete specific requirements of a product backlog item. When we have our product backlog ready and when a team is ready for next sprint, they pull the priority user stories from the product backlog and start estimation for completing the user stories.
Story Point Estimation
In any project, estimation plays a major role. It's very important in terms of the project budget, scope, and also to track the progress of the project against each milestone.
In any project, estimation plays a major role. It's very important in terms of the project budget, scope, and also to track the progress of the project against each milestone.
image source : https://www.youtube.com/watch?v=sCCUEtjCpCs
Estimation is a Team Sport and involves all team members like all developers, designers, testers, deployers on the team is key.
The main benefits of involving the team to estimate is we are giving importance to each member, that satisfies your principles, behind the Agile Manifesto "Build projects around motivated individuals.Give them the environment and support they need, and trust them to get the job done"
As the story points represent the effort to develop a story, the estimate must include all the factors that can affect it like - the amount of work to be done, the complexity of the work, and any risk or uncertainty in doing the work. When estimating with story points, make sure you consider all the above factors.
The main benefits of involving the team to estimate is we are giving importance to each member, that satisfies your principles, behind the Agile Manifesto "Build projects around motivated individuals.Give them the environment and support they need, and trust them to get the job done"
As the story points represent the effort to develop a story, the estimate must include all the factors that can affect it like - the amount of work to be done, the complexity of the work, and any risk or uncertainty in doing the work. When estimating with story points, make sure you consider all the above factors.
Absolute Estimation v/s Relative Estimation
Let's take an example of estimating the following.
If we ask the amount of liquid in ml. of the glass on your left side in the below picture to the team, the answers should be different, some say 100 ml some will say 150 ml. The answers are different but not accurate.
Image Source:https://www.blackpepper.co.uk/what-we-think/blog/agile-vs-waterfall-estimating-planning-tracking
Now, we will ask the 2nd question to the team, like which glass has more liquid. The answer of all the team members is - the left side glass has more liquid.
That means we are good in estimating relatively.
The idea behind the above example is that we might be bad at estimating how many hours it will take to complete a particular requirement, but we are pretty good at saying for example requirement 1 would take twice as long as requirement 2. When team estimates with the story point, they assign a point value to each item.
It's just a value to compare that is assigned - 2 Story points should be twice as much as a story that is assigned 1 Story point.
Now, we will ask the 2nd question to the team, like which glass has more liquid. The answer of all the team members is - the left side glass has more liquid.
That means we are good in estimating relatively.
The idea behind the above example is that we might be bad at estimating how many hours it will take to complete a particular requirement, but we are pretty good at saying for example requirement 1 would take twice as long as requirement 2. When team estimates with the story point, they assign a point value to each item.
It's just a value to compare that is assigned - 2 Story points should be twice as much as a story that is assigned 1 Story point.
image source : https://www.youtube.com/watch?v=sCCUEtjCpCs
How to size a Story
Sizing a story needs efforts from the team. Some of the key points to use as a guideline for estimating a requirement/story are as follow -
How to size a Story
Sizing a story needs efforts from the team. Some of the key points to use as a guideline for estimating a requirement/story are as follow -
Nilesh PatilPosted Oct 30, 2017, 8:54 AM
Nice article sir.........