The Big Freakin' Requirements Document Must Die. Here's Why.
by Chris Gurney
The typical requirements document is a long, sprawling piece of literature. Within it, one might find a title page, table of contents, change history, complex headers and footers, legalese, confidentiality notices, and, if you're lucky, maybe even requirements.
Its length is probably, primarily due to the fact that it tries to be everything to everybody. But, the problem is that this big freaking document isn't read entirely by any single person, except perhaps by the person who wrote it in the first place.
| Attachment | Size |
|---|---|
| The Big Freakin Requirements Document Must Die Here's Why.pdf | 90.74 KB |
Article Sponsored By
Requirements are necessary
Without Requirement documents, customer, product, usecase, system, test etc you will always fail to keep control of your projects and will always end up with time slippping etc. To keep control of these documents is not an easy job and without some sort of requirements software i.e. Requisite Pro or Blueprint you will have a hard time. We are using Requisite Pro at the moment (company policy) but it a bit out-of-date and we are thinking of moving on to something a bit more modern (Blueprint for example). Also I agree the Big Freakin' Requirements document are dead. Requirements should always be there but should be kept as small as possible and using modern software is one one to do this.