Don't rely on the users to be any more prescient than the programmers. Rather than having them sign off on what they think they want ahead of time, work with them (or at least one of them, who becomes the users' representative to the development team) during the project. That way, when you discover that feature X will be N times more difficult to implement than you thought, you can ask them just how useful X would be, and whether it's worth it. Or the user will, after actually using the product for a little while, discover that one of the interface widgets they insisted upon is actually a pain to use. Better to find that before the whole user base starts to whinge....
Moral of this story: Requirements change. Plan for it.
--
F
o
x
t
r
o
t
U
n
i
f
o
r
m
Found a typo in this node? /msg me
The hell with paco, vote for Erudil!
In reply to Re(2): Design Documents?
by FoxtrotUniform
in thread Design Documents?
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |