TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
I chunk based on requirements, feature by feature, and get more
detailed as the requirements become more detailed. It works to clarify
issues quite well...
Of course, this is for planning the general level of effort. The
specifics come as details are fleshed out, specs are written, and
decisions are made.
On 12/28/05, Tony Markos <ajmarkos -at- yahoo -dot- com> wrote:
> Some great comments below! Especially about the need
> to base estimating upon first properly "chunking"
> tasks into right-size [and approx equal-size]
> pieces!!! Of course, the question now is how,
> especially for larger scale systems, does the TW go
> about doing the chunking?
> Hint: No to Forced, artifical chunking (i.e., chunking
> via outlining or "poor man" modeling techniques such
> as Use Cases). Yes to logical, natural partitioning.
HATT List Owner
WWP-Users List Owner
I support Char James-Tanny for STC Secretary.
Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
Help. And online anything else. Redesigned interface with a new
project-based workflow. Try it today! http://www.webworks.com/techwr-l