RTC - Parallel timelines and Teams
502
Five Categories
Five Teams matched to the categories.
100 users
All,
We are rolling out a software solution and are tracking department roll out via RTC. At first, we were doing roll out one department at a time. Now, they want to do parallel releases for some of the smaller depts. and track them separately. This is fine, we can use parallel timelines.
The Question:
If I have 100 people split in the five teams on the "Main Development" timeline, do I have to go and create 5 new teams for each of the additional timelines? Or can I just use the same teams?
Example
Java Team (25 members) on the Main Development timeline. Now there is a Department B timeline, do I need to Create Java Team B or what? How does this affect status and progress bars? Do I have to create new categories?
Five Categories
Five Teams matched to the categories.
100 users
All,
We are rolling out a software solution and are tracking department roll out via RTC. At first, we were doing roll out one department at a time. Now, they want to do parallel releases for some of the smaller depts. and track them separately. This is fine, we can use parallel timelines.
The Question:
If I have 100 people split in the five teams on the "Main Development" timeline, do I have to go and create 5 new teams for each of the additional timelines? Or can I just use the same teams?
Example
Java Team (25 members) on the Main Development timeline. Now there is a Department B timeline, do I need to Create Java Team B or what? How does this affect status and progress bars? Do I have to create new categories?
2 answers
Please see: https://jazz.net/wiki/bin/view/Deployment/RTCProcessFundamentals
The project area defines one or more timelines which define how a given planned period of time is partitioned into iterations such as releases, milestones, sprints etc. A project area can be assigned to exactly one project timeline to work against at any instance in time.
Team areas contained in a project can also each be assigned to exactly one timeline to work against at any instance in time. Only team areas on the top level of the team area hierarchy can specify a different timeline, nested team areas inherit the timeline from their parent. Please see the section Timeline and iteration fundamentals for more details.
So if you want to work against different timelines, you always need one area for each timeline.
The project area defines one or more timelines which define how a given planned period of time is partitioned into iterations such as releases, milestones, sprints etc. A project area can be assigned to exactly one project timeline to work against at any instance in time.
Team areas contained in a project can also each be assigned to exactly one timeline to work against at any instance in time. Only team areas on the top level of the team area hierarchy can specify a different timeline, nested team areas inherit the timeline from their parent. Please see the section Timeline and iteration fundamentals for more details.
So if you want to work against different timelines, you always need one area for each timeline.
I recommend thinking of your team areas as "planning areas" for a given iteration. So if you have a group of people that want to have a separate plan for a given iteration, you'd create a team area for that group of people.
For your particular example, if each of your five teams want to have a separate "departmental plan" for a given iteration in the departmental timeline, then yes, you'd need five additional team areas.
For your particular example, if each of your five teams want to have a separate "departmental plan" for a given iteration in the departmental timeline, then yes, you'd need five additional team areas.
Comments
