Why in CCM is the relationship with teams different for source code, and work items
Why is the relationship 1-many with team assignments to streams and 1-1 in work items? This adds overhead in the project when doing parallel development. Is it planned or possible to allow a 1-many relationship when mapping categories to teams. With the logic that it maps to timelines - teams then categories. It makes it inflexible to deal with the categories being customized based on a timeline and a lot of overhead to create unique teams with the same members over and over again when mapping the categories. It adds overhead for the user in having to allocate their time as well for availability. That availability does not impact source code streams just work items. Any suggestions
One answer
The assignment of a work item to a team allocates the cost of that work item to that team, so that the current load on that team can be calculated. Assigning the same work item to multiple teams would make that calculation ambiguous (which team should get the load, or how should that load be divided amongst the teams?). In addition, it would make it ambiguous which team is actually responsible for the work item. There are no semantic constraints that would limit the number teams that can deliver to a given stream.