Try to split the task into smaller predictable chunks. If you feel some tasks are huge and would involve a lot of code change identifying how it can be split up is important. Once you get smaller tasks it would be much easier to estimate the task, story or epic. Rinse and repeat for some time, and later when you get a story or epic you might be able to relate it to your previous experience and provide a rough estimate. Still you would need to keep estimating and splitting tasks to validate your estimate and evaluate the team’s progress in a measurable way. If you prefer using Fibonacci, you can for example make a cut off point sbove which the task is complex and mist be split. I generally take 8 point and if a task is 8 or more, I won’t work on it until it is split up into smaller independent tasks.
Try to split the task into smaller predictable chunks. If you feel some tasks are huge and would involve a lot of code change identifying how it can be split up is important. Once you get smaller tasks it would be much easier to estimate the task, story or epic. Rinse and repeat for some time, and later when you get a story or epic you might be able to relate it to your previous experience and provide a rough estimate. Still you would need to keep estimating and splitting tasks to validate your estimate and evaluate the team’s progress in a measurable way. If you prefer using Fibonacci, you can for example make a cut off point sbove which the task is complex and mist be split. I generally take 8 point and if a task is 8 or more, I won’t work on it until it is split up into smaller independent tasks.
Thanks for insightful info @sirajulm !