project timeline
If I have developers working on both of these two timelines in parallel, what does this "project timeline" mean? One in active, another not?
For example, a project with both new product release development and current product maintenance might define these two efforts in separate timelines because they have different delivery schedules, teams, and processes.
You can designate one of your timelines as the project timeline.
You can designate one of your timelines as the project timeline.
One answer
Every team area has exactly one timeline that it works on.
Any work done directly in the project area (as opposed to in a team area
below the project area) is done in the "project timeline".
Each top level team area can specify what timeline it wants to work on
(which is inherited by all of its child team areas).
The timeline of a newly created top level team area is initialized to be
the current "project timeline".
Cheers,
Geoff
On 12/13/2011 11:53 AM, hujirong wrote:
Any work done directly in the project area (as opposed to in a team area
below the project area) is done in the "project timeline".
Each top level team area can specify what timeline it wants to work on
(which is inherited by all of its child team areas).
The timeline of a newly created top level team area is initialized to be
the current "project timeline".
Cheers,
Geoff
On 12/13/2011 11:53 AM, hujirong wrote:
If I have developers working on both of these two timelines in
parallel, what does this "project timeline" mean? One in
active, another not?
For example, a project with both new product release
development and current product maintenance might define these two
efforts in separate timelines because they have different delivery
schedules, teams, and processes.
You can designate one of your timelines as the project
timeline.
Comments
I am curious how you deal with it - working on parallel timelines?
If you work in different teams, they can have different timelines. You are allocated with a certain percentage to a team. If you work in teams with different timelines, you basically can work like 20% on one and 30% on another. Team I might do bi-weekly sprints and team 2 monthly. RTC can be configured that way and calculates load etc. based on the data. You have to be member on both teams and RTC can handle that.