I. Overview
- In the practical case, there are always cases where spent time will exceed the estimated time, and this is extremely common, it is not to be missed for any individual or organization.
- For tasks with difficult and temporary tasks, such as the logic of money transfer, etc., the impossible to estimate and estimate the wrong components can easily affect the overall work.
- If we use the hour unit to estimate, it will be easy for customers to “swear”: v. So use story points instead to help reduce the commitment and separate it from estimating over time.
II. What is the story point?
- Simply put, it is a unit to calculate the difficulty of a task to complete.
- As for points, there is no need to distinguish between new, old, senior, junior, etc. Because points are not hours, one person can do 5 points in one day – corresponding to two tasks. , others are 3 points – 1 task.
- It will be calculated according to each sprint, how many points our team will solve, with how many tasks.
- This will help reduce the pressure for newcomers to the project, or those who are still unsure, they will still complete their work with the ability they currently have. And when talking to your boss about your task, it’s easier said than estimating by the hour.
III. Why shouldn’t hours be used?
- As mentioned above, when we estimate by the hour, the fact that we have not shaped the work, but has a specific number of hours for that task, is invisible as a deadline for our necks, causing constant stress. occurs if the task has an unexpected issue and we can’t cover it.
- Some options are just more effort to make your estimates accurate, but to do this correctly you need to research, revise and forecast potential pitfalls and are often Stuck to give a realistic figure. This makes you lose agility, takes more time and can still be wrong in the end.
- When you do the task, you only need 90% to create the code, and the remaining 10% is devoted to fixing bugs, fixing issues, finding bugs, logical cover, etc.But 90% only takes 10 minutes and 10 % will take up to 17 hours.
- Story points allow mistakes and take into account these unspecified factors.
IV. Consider the story point
- It sounds confusing, but it can really easily depict a range of factors that are hard to identify with time alone (this word doesn’t translate so it should be temporary: v).
- Effort
- Amount of work
- Risk
- Uncertainty
- Complexity
- Different departments point of view
- All of this is almost a common benchmark for assessing how many points the task has.
- It is not always possible for the team to have the same number of points, it depends on how each person approached in the task.
- In a planning poker, group programmers can estimate this story to only have two points, because adding a column to the database table is a minor change for them. However, for testers it is possible to estimate this story at 13 points, because it is enough to cause a deadly issue if the data is not as accurate as that column and it has a foreign key link and is not null.
V. How to estimate story points
- Each company, each project will have different applications, but for me this method is quite ok, we will find 3 story points with criteria 1 easy, 1 medium, 1 difficult. Then from these 3 criteria we will identify other tasks that have equal difficulty, easier or harder and then give the appropriate number of points for the task.
BECAUSE. Conclusion
Story points allow for inaccuracies, in a world where accurate estimates are difficult, time-consuming and impossible to make. The key is to turn focus away from time, into an abstract unit that prevents attachment and wasting emotions. Make sure you take into account the required effort, any potential for uncertainty and the risk of actually performing the task when considering the number of story points. This allows your team to quickly estimate stories, highlight potential pitfalls and ensure a sensitive mind approach to estimation. Planning poker is improved with healthy debate and sharing of high-level solutions or solutions.
VII. Refer
https://medium.com/scrumi/story-point-estimation-eli5-a1309a12775e