Here is how I assumed story points would relate to the task, but this takes into consideration 2 facts 1. The team is at least 60-70% aware of what needs to be

Here is how I assumed story points would relate to the task, but this takes into consideration 2 facts 1. The team is at least 60-70% aware of what needs to be built, be it a new feature or changes to an existing one. This does not imply every single member should have the same awareness, but more would be more helpful. 2. If the team is not well equipped then it would require them to research about the task at hand and gain a rough idea before estimating. If you do not have access to this time, then buy it. Coming to the story point wrt to task complexity aspect, here is how I see it, 1. 1 => minor code changes, such as consolidating migration files, css changes that do not involve a parent component or moving config keys for a new feature to a store. Tasks with 1 SP are usually sub tasks based on what I have seen. 2. 2 => minor code changes that involve QA testing the change specifically. This might also include a change in assertion for a test case or adding a new test case to cover this scenario. 3. 3 => Code changes that involve QA testing as well as adding new test cases since this will involving adding new behaviour to a user flow. 4. 5 => Same as for SP(3) but has code changes that involve refactoring or might end up touching dependent files or APIs. Could also be related to adding a new user flow. Might scale to an 8 if the QA feels that testing from their side might be more complex. 5. 8 => Tasks that involves adding a new user flow(s) or refactoring existing flow(s). Any task that involves the QA going `hmmm` during estimation. 6. 13 => Any task 13 or over needs to be split up. One could identify such tasks by checking if the acceptance criteria is similar to a `Give Yourself Goosebumps` novel. I have not included SP wrt to research tasks that would aid a team in understanding how to estimate a new feature because even I throw a 5 or 8 at it. P.S. This is how I saw it, but was never able to fully have the team use it, hence I cannot vouch how effective this might be in the long run