Scope: Adding Sub Tasks during active sprint

[Charles Galoppe]

Scenario: During sprint planing you pull in 5 stories into the sprint. You break each story into a subtasks. You are estimating using "original  time estimate". You then start the sprint. A few days goes by and the dev team realizes they for got to add a sub task to one of the stories. 

Question: Would the subtask be considered adding scope? 

My thoughts:

1. If you pull up the sprint report only "issues" how up with an asterisk, so no it wouldn't add scope.

2. It wouldn't add scope because if you add a subtask to a story and put time against the sub task Jira does not aggregate the time into the story.  

Thoughts? 

[Ollie Guan]

Hi @Charles Galoppe ,

I don't think this is a change in scope, but you need to re-split and estimate the subtasks.

The iteration goal is unchanged, but we have missed some tasks at the beginning of the sprint before re-estimating，the burndown chart will be affected by some fluctuations.

[Charles Galoppe]

That's what I'm thinking also. Please confirm that the burndown would only be impacted if you changed the estimate in the task NOT the sub task because the time tracking in the sub task does not impact the burndown.