Let developers estimate their own work Any system where management writes a schedule and hands it off to programmers is doomed to fail. Only the programmer who is going to do the work can figure out what steps they will need to take to implement that feature. And only the programmer can estimate how long […]

The time-tracking features in FogBugz were designed specifically to feed data into EBS so that it can give you accurate predictions of when your project will ship. Out of the box, there aren’t any built-in reports on the time intervals you enter. If you use FogBugz to track contract-based work for clients, or otherwise have need for timesheet […]

Imagine the following scenario: When a new project is started, many tasks could be 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 reflect more […]

Remove an estimate from your Estimate History To remove a bad, worst, or outlier from your estimation history, go to Schedules > My estimation history > and click the trash/recycle bin icon for the bad estimate. Note that the list is only built when you have at least 10 estimate-vs-actuals in your history. See also […]

Certain statuses in FogBugz make your time estimates and time tracking eligible for consideration in the calculations by Evidence Based Scheduling (EBS). By default, these statuses (and categories) apply: Bug: Resolved (Fixed) Feature: Resolved (Implemented) Inquiry: Resolved (Responded) Schedule Item: Resolved (Completed)  These can be configured by editing the status itself. Click  (or “Admin” if you’re […]