feasability of 2 (or more) development lines to a team area

I suggest thinking of a "team area" as a "process area for a team", i.e.
the place where the process for a particular team is defined. Since
each development line can have a different process defined for it, it
wouldn't make sense to try to associate a team area with two different
development lines (it would be ambiguous which development line's
process would be used to define the process for that team area).

Cheers,
Geoff

chrisr wrote:

I will open an enhancement request, but I wanted to see if it was at
all feasible first. Right now, I think it is only possible to link a
team area to one development line. For a number of teams that I
support, I think it would be useful to be able to indicate that a
particular team should be associated with multiple development lines.
I know a particular user can be part of multiple teams, and it would
probably be ok to go that route, but it would be cleaner I think to
have the team be multiply linked. If this breaks some basic rule in
the RTC workflow though, then please let me know and I won't bother
opening the request.

Thanks,
Chris

Geoffrey Clemm wrote:

I suggest thinking of a "team area" as a "process area for a team", i.e.
the place where the process for a particular team is defined. Since
each development line can have a different process defined for it, it
wouldn't make sense to try to associate a team area with two different
development lines (it would be ambiguous which development line's
process would be used to define the process for that team area).

Cheers,
Geoff

chrisr wrote:
I will open an enhancement request, but I wanted to see if it was at
all feasible first. Right now, I think it is only possible to link a
team area to one development line. For a number of teams that I
support, I think it would be useful to be able to indicate that a
particular team should be associated with multiple development lines.
I know a particular user can be part of multiple teams, and it would
probably be ok to go that route, but it would be cleaner I think to
have the team be multiply linked. If this breaks some basic rule in
the RTC workflow though, then please let me know and I won't bother
opening the request.

Thanks,
Chris

Hi Geoffrey,

We have some users with a similar need. They have a very complex team
heirarchy, and the identical team structure works across many lines of
development at the same time. The impact of needing to copy and
maintain the same team hierarchy over and over is a negative factor in
their adoption of RTC.

Is there at least an automated way to duplicate a team hierarchy for
another timeline?

Thanks!

The short answer is, no, there is no way I am aware of for duplicating a
team hierarchy for a different timeline.

To delve a bit into the detailed requirements here, is it just that you
want to initialize the team hierarchy, but from then on you want to
maintain them separately, or do you want these team hierarchies to
effectively be shared, so when you change membership or roles, it is
reflected in all the timelines?

(And I assume these are all timelines in a single project area ... if
they were in different project areas, sharing or even initializing
becomes difficult, because the roles in one project area can be
completely different from the roles in a different project area).

Cheers,
Geoff

Mark Ingebretson wrote:

Geoffrey Clemm wrote:
I suggest thinking of a "team area" as a "process area for a team",
i.e. the place where the process for a particular team is defined.
Since each development line can have a different process defined for
it, it wouldn't make sense to try to associate a team area with two
different development lines (it would be ambiguous which development
line's process would be used to define the process for that team area).

Cheers,
Geoff

chrisr wrote:
I will open an enhancement request, but I wanted to see if it was at
all feasible first. Right now, I think it is only possible to link a
team area to one development line. For a number of teams that I
support, I think it would be useful to be able to indicate that a
particular team should be associated with multiple development lines.
I know a particular user can be part of multiple teams, and it would
probably be ok to go that route, but it would be cleaner I think to
have the team be multiply linked. If this breaks some basic rule in
the RTC workflow though, then please let me know and I won't bother
opening the request.

Thanks,
Chris


Hi Geoffrey,

We have some users with a similar need. They have a very complex team
heirarchy, and the identical team structure works across many lines of
development at the same time. The impact of needing to copy and
maintain the same team hierarchy over and over is a negative factor in
their adoption of RTC.

Is there at least an automated way to duplicate a team hierarchy for
another timeline?

Thanks!

Geoff,

Right, this is all within a single project area.

Ideally there would be one set of teams for all the timelines. Anything
that could be done to share teams across multiple timelines is what is
needed. Regardless of which iteration/timeline is selected in the
Planned For field of the work item, they want to be able to select from
that same complex list of teams. I think this also applies to selecting
the team when creating a team's iteration plan.


Geoffrey Clemm wrote:

The short answer is, no, there is no way I am aware of for duplicating a
team hierarchy for a different timeline.

To delve a bit into the detailed requirements here, is it just that you
want to initialize the team hierarchy, but from then on you want to
maintain them separately, or do you want these team hierarchies to
effectively be shared, so when you change membership or roles, it is
reflected in all the timelines?

(And I assume these are all timelines in a single project area ... if
they were in different project areas, sharing or even initializing
becomes difficult, because the roles in one project area can be
completely different from the roles in a different project area).

Cheers,
Geoff

Mark Ingebretson wrote:
Geoffrey Clemm wrote:
I suggest thinking of a "team area" as a "process area for a team",
i.e. the place where the process for a particular team is defined.
Since each development line can have a different process defined for
it, it wouldn't make sense to try to associate a team area with two
different development lines (it would be ambiguous which development
line's process would be used to define the process for that team area).

Cheers,
Geoff

chrisr wrote:
I will open an enhancement request, but I wanted to see if it was at
all feasible first. Right now, I think it is only possible to link a
team area to one development line. For a number of teams that I
support, I think it would be useful to be able to indicate that a
particular team should be associated with multiple development lines.
I know a particular user can be part of multiple teams, and it would
probably be ok to go that route, but it would be cleaner I think to
have the team be multiply linked. If this breaks some basic rule in
the RTC workflow though, then please let me know and I won't bother
opening the request.

Thanks,
Chris


Hi Geoffrey,

We have some users with a similar need. They have a very complex team
heirarchy, and the identical team structure works across many lines of
development at the same time. The impact of needing to copy and
maintain the same team hierarchy over and over is a negative factor
in their adoption of RTC.

Is there at least an automated way to duplicate a team hierarchy for
another timeline?

Thanks!

Some sort of multi-development line capability per team would be a major bonus to us too. We have a load of releases - all being released on a different rhythm. For each of these releases we have a different timeline to accommodate the difference in cadence.

This means we have to have artificial teams for each timeline and juggle the proportion of time for each team member allotted to each one which is a major pain.

Hi Geoffrey,

We've just run in to this exact problem. Going forward we are going to have one team developing our next release and servicing the current release at the same time. This is going to potentially require three parallel timelines, all worked on by the same set of people.

Was a formal requirement raised for this? If so, is there is a reference number?

Thanks.

Yes, I submitted an enhancement request for this: work item 99436 "Allow
a Team Area to be associated with multiple timelines"

Please feel free to add your support/interest as a comment.

Cheers,
Geoff

tevans wrote:

Hi Geoffrey,

We've just run in to this exact problem. Going forward we are going to
have one team developing our next release and servicing the current
release at the same time. This is going to potentially require three
parallel timelines, all worked on by the same set of people.

Was a formal requirement raised for this? If so, is there is a
reference number?

Thanks.