|
who is seriously doing this ??
I mean, who is doing this except for a joke, or only because the client requires as a delivery, not only the binaries but the functional documents ?
|
|
|
|
|
Sometimes it's easier to complete the project and then create any docs. You shouldn't change docs continuously in this case.
|
|
|
|
|
Always it's easier to complete the project, and then create the docs.
But... it's wrong and pointless.
How do you plan to show the work is done and charge for it, when nothing is specified?
A buffalo soldier, a dread-like rasta !
|
|
|
|
|
Specs written before requirements gathering are obsolete after.
Specs written before brainstorming are obsolete after.
Specs written before prototyping are obsolete after.
Specs written before implementation are obsolete after.
...
Citizen 20.1.01 'The question is,' said Humpty Dumpty, 'which is to be master - that's all.'
|
|
|
|
|
Heh, I did that once. Delivered a project, client loved it and then they asked for The Spec for their records. We hastily compiled it from the various emails and paper notes we had.
regards,
Paul Watson
Ireland & South Africa
Fernando A. Gomez F. wrote: At least he achieved immortality for a few years.
|
|
|
|
|
I once wrote a set of Superbase apps (6 modules loosley related) which were in production for 4 years when the client wanted one rewritten into Delphi (their new corporate standard) and asked for the specs. They ended up paying more for the specs than the original cost of development.
It was never written in Delphi as the then manager was sacked and it all dissapeared down a black hole.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
toxcct wrote: only because the client requires
That's actually pretty common, from a contractual obligation standpoint.
|
|
|
|
|
that's a reason then for which people should write the specs since the beginning of the project...
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
