Can't wait until VSTS and TFS 2010 to have hierarchical work items? There's a way around this, provided you're ready to use either Microsoft Excel or Microsoft Project to do work item tracking. Introducing Area Paths Area Paths allow architects to clearly define portions of an application as independent subsystems. You do this through a tree-view interface. How do you access Area Paths in TFS? Using the Team Explorer Client Right click on your project in Team Explorer and select "Team Project Settings", then "Areas and Iterations". You can organize Area Paths and Iteration Paths in an unlimited hierarchical view using the provided TreeView. Using Team System Web Access You may also modify Area Paths and Iteration Paths using Team System Web Access. To do so, use the Settings menu on the right side of your screen. Select "Team Project" and then "Areas" or "Iterations". Adding Tasks to TFSWhen adding tasks to TFS, be sure to choose the area path and iteration path that you wish each task to follow. I find it best if you number the paths (1, 1.1, 1.1.1, etc.) so that you can sort by area path easily. After you do so, you'll have a query of work items in your development cycle that looks something like this: I've removed a client name here for privacy purposes, and hopefully your screen won't have a big white blob all over it. This certainly makes things easier to organize inside TFS, but what about viewing this data in a hierarchy? Enter Microsoft ProjectSome great functionality in TFS is it's ability to link data automatically with Excel and Project. The publish/refresh model is extremely light, fast and easy to use. First, you'll need to import work items in to your project plan. It's easy, just click the "Get Work Items" button from the toolbar in project. Next, you'll need to add the headers/hierarchy back in from your area path in Microsoft Project. You can do so by: Pressing Ins in the task list (a new row appears). Type the name of your new task Highlight the sub-tasks below it, and use the indent arrow button (or Tab) to make them subordinate to the header above Repeat this process for multiple levels Make sure to take your new header tasks aren't published to TFS (since the subordinate tasks already are). How do you do this? Add the Publish and Refresh column to your view in project (if it's not already there). Simply set the option to "No" for your header rows. When you're all done, you should have a view in Microsoft project that looks something like this (I've collapsed some of the headers for effect): Technorati Tags: VSTS,TFS,Microsoft Project,Area Paths