Best practices for SubTeam Areas
We're looking at doing most of the feature planning for our next release in RTC. For this release, we've managed to stumble along with a single TeamArea, but the next project is larger - there figure to be 100 or so people on the aggregate team.
So what organization of sub teams makes sense, in practice?
So what organization of sub teams makes sense, in practice?
One answer
I suggest you base your sub-team structure on the groups of people
require/desire to have their own "plan".
Cheers,
Geoff
On 11/1/2010 6:23 PM, Danil wrote:
require/desire to have their own "plan".
Cheers,
Geoff
On 11/1/2010 6:23 PM, Danil wrote:
We're looking at doing most of the feature planning for our next
release in RTC. For this release, we've managed to stumble along
with a single TeamArea, but the next project is larger - there figure
to be 100 or so people on the aggregate team.
So what organization of sub teams makes sense, in practice?