A known gap in the Visual Studio Team System / Team Foundation Server coverage of Application Life Cycle Management (“ALM”) is requirements.
This tool facilitates the story-boarding (scenario) aspect of requirements. That in conjunction with the “list” oriented requirements gives good coverage of what’s needed and now provides full capabilities for the full ALM.
I’ve been doing Agile oriented software development for 6 years, even though we didn’t have names like “Agile” and “XP” when we started. Getting good ideas of the scenarios down and visible to both users and implementers is a key benefit and critical success factor. Doing mockups, scenarios, etc. in unmanaged tools makes keeping these things tracked, updated, and consistent that much harder. This is why VSTS exists, get it all down in a full-round-trip tool (at least for the static stuff) that takes most of the administration headaches away from people trying to get things done.
Elaborate and validate software requirements in Team System projects, and generate storyboards, specifications, work items and tests
stpsoft - the software requirements company.