Burndown by Project & Release dates

Question

I have a scenario where we have multiple projects on the same team with the same team members and each project has a different release date. We would like to track the burndown for the work done per project and its release date to ensure we are on track
for the release. Also we need to know the overall individual team member capacity across the projects to identify if resources can be shared and thus they all have to be under the same Team. Is there a way to have multiple burndowns in Visual Studio Online?
We are using the Agile Project Management template. We previously achieved this by using pivot tables in Excel. But were hoping there is an easier way when using VSO so that we do not have to manage data separately in excel sheets.
Here's my scenario:
Sprint April
Project 1 under Team A. Release Date say April 10 - Burndown 1
Project 2 under Team A. Release Date say April 25 - Burndown 2
Project 3 under Team A. Release Date say May 15 - Burndown 3
What are my options here? Should I create multiple area paths and iteration paths? Have different team projects under the same collection? Please advise
Thanks
pooja dave

Answer 1

There are multiple ways to get something in this direction. The simplest would be to create 3 teams, one for each project, and put all the work for each team in its own Area. Your actual team (the people) can still use the root team (which can be configured
to show all the work) to plan their work across the different projects.
If you want to see the work on the burndown, you can then simply open the team dashboard for each individual team (work area/project) to see the status of the work in progress for each project.
You can also use the Team explorer integration into Excel to export all the data to a table that automatically updates when you hit refresh in Excel. That way you won't need to manage the data in 2 locations, just keep the data in TFS, and then use the Team
tab in excel to update your report.
Using different team project would also work, but makes it much harder for the team members to use the planning tools, there is no way in TFS to get a plan board or backlog view that goes across team projects.
My blog: blog.jessehouwing.nl