Loading Profile...
Starting tasks without point values.
I'd like to be able to start tasks without giving them a value - or at least mark that as "under inspection"
For a lot of tasks, I need to start them just to figure out what the point value is.
The only way I can handle this is by assigning a point value to start the task, starting it and saying that it is "under inspection", and then adjusting the point value. I'd rather not suggest that a task ever had the initial point value, or have it affect my projected workflow until that has been correctly estimated.
For a lot of tasks, I need to start them just to figure out what the point value is.
The only way I can handle this is by assigning a point value to start the task, starting it and saying that it is "under inspection", and then adjusting the point value. I'd rather not suggest that a task ever had the initial point value, or have it affect my projected workflow until that has been correctly estimated.
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.
The company marked this question as answered.
-
Inappropriate?In the past a story that cant be acurately estimated until we have started working on it we try to over estimate e.g. "it couldn't be more than 5 points" then when we start working on it we lower the estimate if appropriate.
Another school of thought is that you should leave it unestimated and create a chore to "research such and such a problem" and use that story to figure out the problem space enough to be able to estimate the actual feature story.
