Re: Estimating a Task Analysis

Subject: Re: Estimating a Task Analysis
From: "Leslie Johnson" <custcomm -at- cadvision -dot- com>
To: <TECHWR-L -at- lists -dot- raycomm -dot- com>
Date: Fri, 3 Sep 1999 15:18:04 -0600

Anthony Markatos wrote:

"Based upon this 30% rule, a 3 - 5 day task analysis should result in a
manual taking from 9 to 15 days. It usually takes me many months (if not a
year) to write the manual for a complex software package."

Hi Anthony,

Good catch! What I neglected to say is that the Task Analysis isn't really
part of the project. We, too, use a 30% rule, but we split our projects into
Analysis & Design, Development, and Production, with each taking about 1/3
of the time. The Task Analysis is a really short and abbreviated (another
way of saying "down and dirty") preliminary mini-project, which we do before
we begin the project itself. When the Task Analysis is completed (and we
don't do a Task Analysis for all our projects - often clients know exactly
what they want and exactly how they want it done), we deliver a report with
an estimate for the Analysis & Design portion (where we create our
prototype).

I hope this clears up any misunderstandings.

Leslie Johnson
S.I. Writes
Calgary, Alberta





Previous by Author: Re: Estimating a Task Analysis
Next by Author: Re: Process, not bureaucracy
Previous by Thread: Re: Estimating a Task Analysis
Next by Thread: what do you do?


What this post helpful? Share it with friends and colleagues:

Sponsored Ads


Sponsored Ads