Story Work Item shows estimation fields in plan preview only
I noticed that the Story WI does not display the estimate, correction,
or time spent fields except when previewed in a plan. Can anyone shed
any light on that, please (beta 3).
In the preview pane you can enter values and save and they are reflected
in the time span of the story progress bar. I am not sure how this might
relate/affect estimates in any subtasks of the story.
OTOH, I have heard customer need for a preliminary estimation value for
a story.
Thanks.
Jim D'Anjou
or time spent fields except when previewed in a plan. Can anyone shed
any light on that, please (beta 3).
In the preview pane you can enter values and save and they are reflected
in the time span of the story progress bar. I am not sure how this might
relate/affect estimates in any subtasks of the story.
OTOH, I have heard customer need for a preliminary estimation value for
a story.
Thanks.
Jim D'Anjou
One answer
Hi Jim,
We treat stories as top level work item types which means that they
usually describe a high level work unit which can be broken up into
further (implementing) tasks. Instead of estimating all work in the
story, each subtask should be estimated. Setting an estimate on a story
should only be used to reflect the time it will take to manage the
story, e.g. breaking it up into tasks, assigning subtask to users,
organizing required resources, ...
The complexity attribute could be used here. Based on a preliminary
estimation, story points can be assigned. There is a report called
'Story Points by Iteration' which will show the achieved story point per
iteration.
--
Cheers, Johannes
Agile Planning Team
I noticed that the Story WI does not display the estimate, correction,
or time spent fields except when previewed in a plan. Can anyone shed
any light on that, please (beta 3).
In the preview pane you can enter values and save and they are reflected
in the time span of the story progress bar. I am not sure how this might
relate/affect estimates in any subtasks of the story.
We treat stories as top level work item types which means that they
usually describe a high level work unit which can be broken up into
further (implementing) tasks. Instead of estimating all work in the
story, each subtask should be estimated. Setting an estimate on a story
should only be used to reflect the time it will take to manage the
story, e.g. breaking it up into tasks, assigning subtask to users,
organizing required resources, ...
OTOH, I have heard customer need for a preliminary estimation value for
a story.
The complexity attribute could be used here. Based on a preliminary
estimation, story points can be assigned. There is a report called
'Story Points by Iteration' which will show the achieved story point per
iteration.
--
Cheers, Johannes
Agile Planning Team