After Greenhopper sprint is formed and is underway, developers realize some subtasks that were not added. Adding of those sub tasks is now considered scope change by Greenhopper. Is it possibel to exclude this from "scope change" definition?
As of now it looks like this can't be done.
We have the problem, but not a big issue because:
Without it, we will have a problem on #2.
I guess the answer is No. But the problem is more practical.
Thing is not always the new subtasks indicate a scope change. But because they are marked as scope change, there are just too many subtasks marked as scope change and we miss the real message.
I agree with Nimitt. At the least there should be a choice of whether or not to create a subtask as added scope.
Sometimes we want to add subtasks to breakdown the problem better, and it doesn't necessarily mean we added more work.
It looks like you're new here. Sign in or register to get started.
