|
10 Top Reasons for Not Doing Requirements10. We don't need requirements, we're using objects/java/web/... 9. The users don't know what they want 8. We already know what the users want 7. Who cares what the users want? 6. We don't have time to do requirements 5. It's too hard to do requirements 4. My boss frowns when I write requirements 3. The problem is too complex to write requirements 2. It's easier the change the system later than to do the requirements up front 1. We have already started writing code, and we don't want to spoil it download pdf file This work is copyright © 1995 - 2002 Atlantic Systems Guild Limited, but may be adapted for your internal use provided copyright is acknowledged. Please let us know what you are using it for. |