Eliminating requirement for defect estimates?
When we open our plans, we get a message that there are "problems detected" and all our defects show up with a warning yellow triangle by them. The warning is "The work item is planned but has no estimate specified."
We are not putting estimates in our defects. How do we configure RTC to eliminate this message and eliminate the requirement for an estimate on a defect?
We are not putting estimates in our defects. How do we configure RTC to eliminate this message and eliminate the requirement for an estimate on a defect?
3 answers
If you aren't putting estimates on your defects, how do you track and
measure progress against your defect backlog?
Cheers,
Geoff
On 9/16/2010 12:23 PM, harrismd wrote:
measure progress against your defect backlog?
Cheers,
Geoff
On 9/16/2010 12:23 PM, harrismd wrote:
When we open our plans, we get a message that there are "problems
detected" and all our defects show up with a warning yellow
triangle by them. The warning is "The work item is planned but
has no estimate specified."
We are not putting estimates in our defects. How do we configure RTC
to eliminate this message and eliminate the requirement for an
estimate on a defect?
We only measure progress by total number of defects fixed. Decisions about whether a defect goes into the current iteration backlog is done based upon a gut feeling and whether or not it is considered "must fix". The decision has no real basis in if it is actually possible to fix the defect in the iteration. At the end of the iteration, whatever defects didn't get fixed, they're simply dumped in the next iteration backlog. No, it's not SCRUM, but it's where we are. If we took the time to investigate the defect enough to have an accurate estimate, most times we could have already fixed it.
Do we just have to learn to ignore the warnings?
Do we just have to learn to ignore the warnings?
Just thinking out loud ... you can contribute process actions on "save
work item" ... so if your process action initialized the estimate to
some standard value, then you wouldn't get the warning.
Alternatively, you could periodically just run a query that selects all
defects that don't have an estimate, multi-select them all, and set an
estimate on all of them.
Cheers,
Geoff
On 9/17/2010 12:38 PM, harrismd wrote:
work item" ... so if your process action initialized the estimate to
some standard value, then you wouldn't get the warning.
Alternatively, you could periodically just run a query that selects all
defects that don't have an estimate, multi-select them all, and set an
estimate on all of them.
Cheers,
Geoff
On 9/17/2010 12:38 PM, harrismd wrote:
We only measure progress by total number of defects fixed. Decisions
about whether a defect goes into the current iteration backlog is
done based upon a gut feeling and whether or not it is considered
"must fix". The decision has no real basis in if it is
actually possible to fix the defect in the iteration. At the end of
the iteration, whatever defects didn't get fixed, they're simply
dumped in the next iteration backlog. No, it's not SCRUM, but it's
where we are. If we took the time to investigate the defect enough
to have an accurate estimate, most times we could have already fixed
it.
Do we just have to learn to ignore the warnings?