Is it normal for all tasks to move over to the Current container on a new iteration start day?
Today is the day when we start our new iteration and, like last iteration, all our tasks have moved over to the Current container and there's nothing in the Backlog container and we can't move anything in to it either. If we wait for about half a day then things going back to normal so I'm wondering is this expected behavior?
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
-
Inappropriate?On the start of a new iteration, Tracker will move stories that are expected to be completed during the "current" iteration based on the projected velocity. The projected velocity is calculated based on previous iterations. The points are based on feature stories not chores and bugs (unless you've decided to estimate bugs and chores). So most likely in your case you do not have enough feature points in your backlog to match the projected velocity, therefore all of the stories are moved to current. As you estimate stories in current you end up and reaching the projected velocity, stories after one that reached the expected velocity are pushed back into the backlog.
But is it not normal behavior for stories to move into and out of the current panel if there is not any story changes, estimating, etc.
Mark
Loading Profile...

