Re: Estimating/Budgeting

["Bruce H. Johnson" <corpknow -at- EARTHLINK -dot- NET>]

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

>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
do
more (almost inevitable) you can point out that this is an addition and
more
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
http://www.legendcomm.com


-------------

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>
http://www.business1.com/cki/

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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