Team Areas
One answer
What I usually recommend is that team areas be defined in terms of
"units of planning", i.e. a team consists of the group of people that
share a common iteration/sprint plan. In most cases, this aligns with
the organizational team boundaries, in which case the "naive" approach
works just fine.
Cheers,
Geoff
On 7/7/2010 12:23 PM, Danil wrote:
"units of planning", i.e. a team consists of the group of people that
share a common iteration/sprint plan. In most cases, this aligns with
the organizational team boundaries, in which case the "naive" approach
works just fine.
Cheers,
Geoff
On 7/7/2010 12:23 PM, Danil wrote:
What are the best practices around team areas? Are there surprises
lurking for a team that naively assumes that team and subteam
organization should match the organization of the human team assets?