2. Don't provide "percentage confident" estimates unless you have a quantitatively derived basis for doing so.

3. Don't reduce developer estimates; they're probably too optimistic already.

4. Invest effort in assessing the size of the software (lines of code) that will

be built. Size is the single most significant contributor to project effort and schedule.

5. Don't assume that effort scales up linearly as project size does. Effort scales up exponentially.