Chapter 12

Tip #55 

Use fuzzy logic to estimate program size in lines of code.

Tip #56 

Consider using standard components as a low-effort technique to estimate size in a project's early stages.

Tip #57 

Use story points to obtain an early estimate of an iterative project's effort and schedule that is based on data from the same project.

Tip #58 

Exercise caution when calculating estimates that use numeric ratings scales. Be sure that the numeric categories in the scale actually work like numbers, not like verbal categories such as small, medium, and large.

Tip #59 

Use t-shirt sizing to help nontechnical stakeholders rule features in or out while the project is in the wide part of the Cone of Uncertainty.

Tip #60 

Use proxy-based techniques to estimate test cases, defects, pages of user documentation, and other quantities that are difficult to estimate directly.

Tip #61 

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.