Tools
Top 5 Frustrations of Requirements Docs and Tips to Avoid Them
Every year, the complexity of projects increases. The average requirements document is over 100 pages and changes 20 times during the development process. It’s brutal. That means as a Business Analyst or Project Manager, you likely spend hours circulating, editing and tracking changes to a hefty requirements document with the hope that your team actually stays engaged and reads it. Wishful thinking, right?
Better Platforms for Managing Requirements
In this week's article David Gelperin offers his experiences in using a lightweight requirements management tool. A middle ground between using a word process or spreadsheet (easy) and a capable, but medium to heavyweight requirements management tool based on a database management system. David describes his experiences with a couple of outline procesor tools that result in easy and capable requirements management.
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.
- 26 comments
- 5062 reads
