Re: How will you ensure that your requirement document is complete
That last reply by rehtve is not good enough in my mind. It has been my experience that effective or more complete requirements come from a number of good practices being applied.
Among them, here are a few keys that may not insure that requirements are totally complete, but can give you more assurance that you did the best job during requirements and analysis.
1) Make sure you have folks that really understand the problem you are trying to solve and who is effected by it. Especially make sure they understand who would be effected if you changed soemthing around that problem. This helps you with the next item. Strong business analysts are a great benefit, and unfortunately a lot of companies don't have enough of them.
2) Identify and involve all key stakeholders. Stakeholders are not just people that pay for a project or request it. Key stakeholders should be people effected by the changes.
3) Have requirements walkthroughs before approvals are gained. Walkthroughs with key stakeholders, interested parties, developers, and testing folks help flush out hidden issues and insure all requirements are testable and clear.
These are three key areas we have been focusing on this year to great success.
Hope this helps.
Quality Assurance Manager