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?
We have the problem, but not a big issue because:
Without it, we will have a problem on #2.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot