On Saturday 28 February 2004 11:57 am, Mike Harrison scribbled:
> A good way of reducing this problem is to write your interpretation of =
the
> spec and get the customer to approve it. I have NEVER had a spec from a
> customer that has been sufficiently complete and detailed.

A great way to avoid this is to have the customer provide test cases.  No=
t=20
always do-able -- especially with software projects -- but I have been ab=
le=20
to get them on some projects.  If they pass the test cases, it almost fir=
mly=20
defines that the application has been successfully implemented.

> If they then want 'extras', if possible, convince them to accept delive=
ry
> of the 'basic' version first, then add bells & whistles later.

Ahhhh.... incremental development and/or rapid-application development ..=
=2E my=20
favourite way to do things when possible!  Slurp!  But I'd really say no =
to=20
this on a 1-week-ish project.

Cheers,
-Neil.

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.