Re: Estimating a Project

[Beth Agnew <Beth -dot- Agnew -at- senecac -dot- on -dot- ca>]

That's where we technical communicators can make a real contribution to 
the companies with whom we work. If we start asking for specifications, 
and marketing requirements documents, and design documents, making a 
rational case for why these artifacts are useful to the product 
development process, then we can eventually bring about some improvement 
in that process. It helps our own efforts, and overall contributes to a 
better quality product.

Sometimes it takes a while (a long while!) for an organization to 
understand that building a product "on paper" first saves time and 
resources farther down the line, but once they "get it" life looks a 
whole lot better!

Schermerhorn, Robert wrote: