Requirements Gathering

Just as there is no one right programming language for every application, there is no one right way to develop the more detailed specifications. Different environments call for different techniques, and the requirements managers and requirements writers will probably need to develop a mix of skills suited to various circumstances.

Why can we not allow for a process that creates detailed requirements and design information for each feature so that we can create more meaningful estimates?

Why can we not allow for a process that creates detailed requirements and design information for each feature so that we can create more meaningful estimates? Isn’t that the professional way to approach the problem? If the schedule provides time for more detailed estimating at this time, by all means do it! However, we believe that it is crucial to be able to make some quick decisions about the scope of the activity without a more detailed estimate. Why? Because to do otherwise invests resources in what will later be determined to be “wasted inventory,”