This is a serious issue. At my startup we are tryng hard to find the best
trade off between spec'ing and wasting time. Although I wrote a 200 + page
UI spec for our app, I think the following article is VERY relevant. Here
is an excerpt.
---- Excerpt ----
*Step 1: Don't write a functional specifications document*
Don't write a functional specifications document. Why? Well, there's nothing
functional about a functional specifications document.
Functional specifications documents lead to an illusion of agreement. A
bunch of people agreeing on paragraphs of text is not real agreement.
Everyone is *reading* the same thing, but they're often *thinking* something
different. This inevitably comes out in the future when it's too late.
"Wait, that's not what I had in mind…" "Huh? That's not how we described
it." "Yes it was and we all agreed on it — you even signed off on it." You
know the drill.
The full text can be foud at: http://www.37signals.com/svn/archives/001050.php (make sure you read the
I do a lot of Mocking Up in my work (usually using Director). I find it very
useful in many cases. But I don't think a mockup can be a full replacement
since it takes time and money to mock things up. Still looking for the