What is Story Point? A story point is a measurement, which is used in project management to quickly detect the effort, risk, and complexity of the use of a particular user story. Basically, a number tells everyone on the team how challenging a story is and how much time the team will be required to complete the user story.
Story Point = Risk + Complexity + Effort/Repetition
Steps to give story point to a user story
1. Fibonacci Series and determining the matrix
2. Planning Poker
- In the sprint planning session, each developer and tester receives a set of cards, each showing a Fibonacci sequence number.
- The backlog is brought to the table so that the team can ask questions and clarify the features
- When the discussion is over every team member secretly selects a card that accurately reflects their rating.
- Once all the cards have been selected, the team members present their cards at once. When consensus is reached, it is time to move on to the next thing. When card number vary, the team negotiate until they reach an agreement. And if requires then the team can ask further questions to the product owner
It is always good to have a complexity matrix in hand so that the team members can focus on the timing of the poker setting, as it allows for greater consistency in all activities. Also, it helps to set a maximum limit (13, for example). If the work is estimated to be larger than that limit, it should be divided into smaller items. Similarly, if the task is less than 1, it should be combined into another function
Note:- If the story points are too far away or the team disagrees then it is best to put that user story item back to the product backlog and revisit the user story item if product uncertainty or technical uncertainty is reduced
Best Practices to give story points to a user story in remote working culture:
Running the planning poker game