Managing multiple projects with one backlog and iteration

Edit Subject

It is not possible to manage work items from different projects in the same backlog. Some customers favor using iterations and areas to manage multiple projects instead of multiple Team Projects. This approach is described in a blog post from Martin Hinshelwood. This method would allow you to manage multiple projects from the same backlog in Urban Turtle.

Disappointing. We have a set of aggregate work item queries that do all this nicely, albeit with the one major issue of being ugly/people-unfriendly like all other work-item queries. (The reason we investigating Urban Turtle.)

We re facing the exact same need as you Drew

@Louis Pellerin
Since it is feasible to create the queries representing th information is it a feature that is considered to be included in th road map for Urban Turtle?

@Drew Loika
Have you just kept on using your queries wth the ugly/unfriendliness disadvantage o have you started using Urban Turtle with the lack of requirement fulfillment as disadvantage or some entirely third approach?

There are no current plans to include this in a future version. We prefer staying close to the Team Web Access concept of "single current project" as it makes things simpler for most users.

However, we're always listening to customer feedback. If more people request this, we may consider it.

"Single current project"? Sigh, I wish. Sebastian, the current strategy has been to... do nothing. Long term we're looking forward to the team web access improvements in the next version of Team Foundation Server. In the meantime we're trying to figure out how to build a friendlier project management interface in SharePoint using the TFS web parts. To do this we may have to merge our multiple projects into one project and use Areas to distinguish. (ugh) The interesting part about using SharePoint is that based on the information I've seen about the next TFS release Microsoft is focusing their development on Team Web Access rather than SharePoint. This doesn't fit at ALL with our current strategy/goals so the only advice I can give is that we're probably doing it wrong. Hope that helps!

I don't expect the next version of Team Web Access to allow you to manage a single backlog across multiple projects. I may be wrong though, but from what I've seen, it does not appear to be possible.

We are facing similar problems in our company.
Managing different Scrum teams with one TFS project works fine. We will use Urban Turtle team functionality for that having base areas and so on.

But the defects for all products are tracked in a different TFS project. This is a company wide decision...
Now it would be great to include the defects related to a specific SCRUM team in the related backlog.