My plan is to create some kind of general storypoint measurements which I can either use in my private or freelance projects, at my current company or both. I want to get away from estimating story points through having a certain feel or relying too much on the experience of previous user stories. The goal is to be able to apply a general pattern to simplify estimation and planning poker. Instead of discussions like "I just feel it's a 3" or trying to find a correlation between the length of a user story and its size, the engineering team (or even managers with programming experience) can categorize the user story (and their tasks).
1 Storypoint: Multiple or a single small surgical modifications
Example: Layout modifications, Typo fixes, micro bug fixes
2 Storypoints: Adding a new element with a bit of logic attached to it
Example:
- New unit test
- New route
- New event handler
- New component, screen, etc.
3 Storypoints: Smaller logic
Example: Input validation
Individual tasks can be broken down, categorized and summed up to get the storypoint value of a user story. The side effect is that this will increase the amount of story points that are available in a sprint.
First, do a sprint to get a baseline for how many storypoints you will be able to do in a sprint.