Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?

Submission Summary: 0 pending, 38 declined, 3 accepted (41 total, 7.32% accepted)


+ - Project specifications - what is fair game?

Submitted by
MC68040 writes "Hi slashdot readers, I've been working as a PHP & C programmer for an UK-based IT firm for some time now and I've run in to something of a problem; my manager isn't very it-literate. What this means in the real world is that the specification for what I need to develop for the client often comes out very 'fuzzy' to say the least, and this is not helped by that the client often isn't sure what they really want. This in it's turn leads to many (frustrating) hours of overtime for me and my co-workers. So slashdot readers, what form of "product specification" is fair to ask to from the client? What should we be able to expect them to detail? I'm not talking about 'when you click this button..' but rather in general terms, like 'the form should collect x details, some of these details should also be available from page x, specifically ...'."

The biggest difference between time and space is that you can't reuse time. -- Merrick Furst