Using Estimates to Manage Workload

Estimates are also very useful if you're trying to keep track of the total time left to resolve a group of cases. At the bottom of any list of cases, FogBugz will always calculate a summary of the estimated remaining time for all cases shown in that particular list. If you are careful to maintain estimates and elapsed time as you go along, you can use these summaries to get a good approximation of how much work is left for any set of cases. There are many uses for such a list, depending on which filter you use to construct the list. For example:

• If you're a manager, you can filter for unresolved cases in a particular release to get an estimate of how much work remains to be done to ship that release.

• If you're a manager, you can filter for unresolved cases assigned to particular developers to tell who's overloaded and who's not.

• If you're a developer, you can look at your own cases to see just how overloaded you are.

• If you're a tester, you can see how good a job you're doing at keeping the developers overloaded.

• If you need to make cuts, you can filter by area to see how much work eliminating a particular area would save.

■Tip Summing estimates is most useful when every case that can be estimated has an estimate. Using filters, it is easy to search for all the bugs without estimates so you can add estimates (or ask the appropriate developer to add estimates).

Figure 4-4 shows how FogBugz presents an estimate with a list of cases. Note the summary at the bottom of the page; it includes the total estimated amount of time remaining, as well as the number of cases with no estimate. You can also see the estimates for individual cases by referring to the detailed list.

Figure 4-4. A list of cases with estimates
0 0

Post a comment