April 5, 2011, 11:21 p.m.
posted by concurre
The examples in this chapter have shown how to use proxy-based techniques to estimate lines of code and effort. You could apply the same techniques to estimate test cases, defects, pages of user documentation, or anything else that might be easier to estimate by proxy than to estimate directly.
Use proxy-based techniques to estimate test cases, defects, pages of user documentation, and other quantities that are difficult to estimate directly.
As Chapter 7, "Count, Compute, Judge," described, there is hardly any limit to what you might be able to count. This chapter has presented just a few specific examples. If you believe you have something else in your environment that would be a better indication of project size than fuzzy logic, standard components, or story points, you should count that instead.
Count whatever is easiest to count and provides the most accuracy in your environment, collect calibration data on that, and then use that data to create estimates that are well-suited to your environment.