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
please tell me there's a follow-on article coming
I think every self-respecting BA/Product Manager out there knows that the big honkin' requirements document has to die. The question is, what do we use to replace it? I've worked with teams who've tried many different things, and none seems to do the trick.