My team and I have recently adopted Scrum, and we've chosen Jira as our primary tool for managing sprints and backlogs. As we navigate our sprint planning, we're grappling with an issue related to the estimation of story points and their relationship with sub-tasks.
Here's the challenge:
When creating a user story, we don't always have a full picture of the required sub-tasks. As the sprint progresses and the story is further refined or work begins, more sub-tasks become apparent. We've been assigning story points to each of these sub-tasks based on the anticipated effort. However, when trying to automate the summation of these points to reflect at the parent story level in Jira, we run into a problem. If, for example, a user story ends up having two sub-tasks, each estimated at 5 story points, Jira sums the story points of the parent story (which would be 10) with the sub-tasks, resulting in a total of 20 story points. This not only skews our sprint velocity but also misrepresents our initial estimation.
I realize there's a variety of opinions on whether or not sub-tasks should be assigned story points, but given our evolving understanding of user stories and their subsequent sub-tasks, how can we accurately aggregate the story points in Jira without this double counting? Also, if there's a more efficient strategy for managing story points in relation to emergent sub-tasks, I'd greatly appreciate your insights and recommendations.