The purpose of the Filed-Against property is to automate the assignment
of a work item to a team. So it wouldn't make sense to have two
"filed-against" values, since this would make that mapping ambiguous.

So first decide on your team areas, where you create a team area for
each group of people that will share a common iteration/sprint plan.

Next, decide on a set of "categories" where a category must satisfy two
things:
- all work for that category (for a given timeline) is handled by a
single team (this is a requirement)
- the category name is something that anyone who creates a work item
would be able to select (do the best you can here, given the preceding
requirement ... if you work item creator gets it wrong, the team
receiving the work item will modify the filed-against property so it
gets re-assigned to the right team.

Cheers,
Geoff

On 7/7/2010 10:38 AM, marky wrote:

This is a general question about setting up a team structure using a
matrix organization.

My team is separated as a matrix organization, where we are split
across Product, Release, Component (code base) and Feature Team.

Currently, our teams are split by Release and Component. This allows
a component team, working on a common code base, to use iteration
plans. I want to create Feature Teams that will allow them to use
iteration plans as well. Unfortunately, I have only 1 'Filed
Against' field. Any suggestions on an elegant way to split the team
along Feature team lines and Component team lines?

Thanks,
Mark