Managing Projects with Microsoft® Visual Studio® Team System

Entering Requirements into Visual Studio Team System

It’s virtually impossible to provide estimates on a system without any level of detail of the system unless you are working on a strictly fixed-cost variable-functionality release schedule in which you simply deliver features until you run out of money. Software requirements can take many forms, from screen designs to business and workflow models to usage scenarios and operational needs. Arguably, there is yet to be a single unified method for storing all forms of system requirements. However, Visual Studio Team System allows you to store many of these requirement types as work items. If you are using MSF Agile, you will have two different work items to store your requirements: the Scenario ...