Question

Is it true that when you close a case, the INITIAL estimate is used to update the estimator's adjustment from EBS? That seems like that might pose a problem with our current workflow. Usually, when a new project is started, many tasks are entered by the project manager and then assigned to the appropriate developer. When the developer gets the case, the first thing they do is revise the estimate to reflect what their real expectation is. Often, the initial tasks are wildly wrong since they are more a guess of schedule than effort. If the initial estimate is used to adjust the person's performance, that seems very inaccurate.

Also, we often find that some cases get handed off many times in order to facilitate team member communication. How does that play into EBS?

Answer 1

Actually, it depends. FB will use the "Original Estimate" and this can actually change from the "first estimate". I'll elaborate:

1. PM enters an estimate of 10 days. (No one has put ANY time against the case yet)
2. PM assigns to Dev. (No one has put ANY time against the case yet)
3. Dev changes estimate to 5 days. (No one has put ANY time against the case yet)
4. Dev puts elapsed time into the case directly into the elapsed time field or via "Working On" function. 5 days becomes the Original Estimate.

---

• FB doesn't count something as the Original Estimate until work is done against the case.
• Once work is done against the case, the existing estimate becomes the Original Estimate (even if it's not the first estimate)
• Whoever entered the estimate that existed at the time work started, will have the case go against their EBS and history.
  • This means that if the Dev hadn't changed the estimate from 10 days, EBS would be based off of the PM. Also, the developers delivery of the case (estimate vs. elapsed) would go into the PM's history, not the developer's. (This is an important distinction if you want to use EBS)
• If you have a true outlier estimate which was way off due to a typo, you can remove the data point from your history

To make sure that the developer's history is used, make sure everyone change the estimate before they start work on a case (Note this only works the first time. You can't change the estimate, start work, change the estimate again, and restart.).

To be safe, I never put in estimates before giving the case to someone. If you have to, then follow the rules above.

Answer 2

Yes, it's true.

The idea is that PMs should NOT estimates tasks, because, well, they are wrong, as you mentioned. Wild guesses are wrong for scheduling. Estimates should be provided by developers.

Personally i think not estimated tasks should be threated as "average" tasks. You can vote for feature here: http://fogbugz.stackexchange.com/questions/1268/feature-request-an-option-to-tell-ebs-to-take-unestimated-cases-into-account

The only thing you can do now is to make developers estimate earlier, or implement some kind of team planning process (we did that).

Answering the second question: if handled task seems too need another estimate and more work - create a subcase.