Take a look at a proposal (Visual Studio Team System User Education : Scenario Topics) from David Chesnut of the Team System User Education Team that looks to replace the current orientation-style topics found in the product documentation with something a bit more useful. As always, your feedback is crucial and greatly appreciated.
To me, scenarios represent something fundamental. Documentation should map technology (e.g. work item lists) into the problem space the user is working in (e.g. to track project progress). These serve the same purpose as an abstract in a lengthy technical document: Telling the reader succinctly the key points of the content section so they can decide if they need to read any further.