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
So what replaces the Big Freakin' Requirements Document? by jwilson1776
Requirements are necessary by grahamwbell
Replacing the BFRD by aporter
the digestable requirements document by sgodfrey
Nothing new said here by fifedog
Suggestion by kjmason
Subtle plug by julie.blake
A Big Freakin Whinge Fest by millerpr5
