AnsweredAssumed Answered

Adding tasks mid-sprint - burndown impact

Question asked by 0518177361869acd72889fd1ab1dae70 on Jun 10, 2015
Latest reply on Jun 11, 2015 by 0e199f0150dc69b94c77533352a21045
When adding a task to a story during sprint execution should we estimate that task or just update the to-do column? I want to make sure that the burndown reflects any change in scope but I'm not sure how Rally calculates the burndown. If we supply an estimate and an equal value for the to-do column, will the burndown show a spike in scope or since the values are the same will it just be absorbed and treated as though the task was there from the beginning?

My initial thought is to have a 0 estimate with a value in the to-do column which would indicate that the task was unplanned, but I'm not sure what the best practice is in this case.

I appreciate the feedback!