FogBugz Technical Support

A forum for technical support discussion related to Fogbugz.
The current FogBugz Knowledge Base can be found at http://help.fogcreek.com/fogbugz.

Posts by Fog Creek Employees are marked:

Documentation
Release Notes
Network Status

Estimate History

Hi,

In the current version of FB, it looks like the person that estimated the case gets the estimate history even if they didn't resolve the case.

This causes us a problem - often in our sprint meetings we will talk about estimates (with FB up on the projector). I'll then fill in the estimate we (or the developer who will do the work) has agreed on, and see how that affects the workload in the sprint. The problem is that because I put in the estimate, FB then messes with my estimate history even though another developer resolved the case!

Is there any way of making sure that the person who resolves (and therefore owns) the case also owns the estimate, even if he or she did not enter the original estimate?

Cheers,

Steve
Steve Baxter Send private email
Thursday, May 14, 2009
 
 
The only way to make sure that the estimate gets "credited" to someone is by having them enter the estimate.
Michael H. Pryor Send private email
Thursday, May 14, 2009
 
 
It'd mean an extra license, but you could have a "Consensus" user you log in as during sprint meetings.  That way, your consensus estimates have their own performance history, and the person doing the typing for the team doesn't build up an estimate history that doesn't reflect their actual performance.

If you don't want to buy another license, it's a bit of a hack, but you could use someone who doesn't customarily enter estimates or bill time, like a support or sales rep.
Rich Armstrong Send private email
Thursday, May 14, 2009
 
 
Out of interest, why is this model followed? I really think the estimate history should be applied to the person that resolves the case, NOT the person that estimated it in the first place.

The onus should be on the person who is working on the case to keep the estimate up to date. The person working on it will resolve it, therefore they should either agree with the existing estimate or update it - either way, the estimate should be applied to their EBS, not the original estimator's.

Cheers,

Steve
Steve Baxter Send private email
Tuesday, June 2, 2009
 
 
Since EBS is a predictive algorithm, we use the original and current estimate to look forward, not the final estimate to look backward.  Make sense?
Rich Armstrong Send private email
Tuesday, June 2, 2009
 
 

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics
 
Powered by FogBugz Bug Tracking and Evidence-Based Scheduling.