Re: Estimating/Budgeting

Subject: Re: Estimating/Budgeting
From: "Bruce H. Johnson" <corpknow -at- EARTHLINK -dot- NET>
Date: Sun, 2 Jun 1996 13:34:16 -0700

>I am replying to the list as my most important lesson/tip seems frequently

>ALWAYS try to break down the task into increments. Ideally, the increments
should be sections such that if your customer/boss decides on having you
more (almost inevitable) you can point out that this is an addition and
money/time/supplies are required.

>Years ago I bid a job in that way for a catalogue of software. The initial
job was described as having 40 programs to test and describe. By the
time of
publication of the first edition, there were about 125 and I was
thanking my
lucky stars for a suspicious nature.

>AverilLegend Communications, Inc.
Makers of PostScript Software


My company always breaks a proposal into lots of detail; setup,
verifcation, data gathering, prototyping, review/changes, production,
delivery, maintenance manual etc., most with our best estimate of time
involved and our assumptions, e.g., 25 procedures. 90% of the time, our
client wants more after the project is under way. With the detail
spelled out in advance, it's a lot easier to show that the changes are
an increase in scope and _will_ cost more.

Bruce H. Johnson
Corporate Knowledge, Inc. -- Your knowledge transfer specialists.
corpknow -at- earthlink -dot- net Los Angeles, California
#include <disclaimer.h>

Post Message: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Get Commands: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "help" in body.
Unsubscribe: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "signoff TECHWR-L"
Listowner: ejray -at- ionet -dot- net

Previous by Author: Re: doc to help theory
Next by Author: InfoViewer-style on-line documentation
Previous by Thread: doc to help theory -Reply
Next by Thread: Re: social science writing

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

Sponsored Ads