Can a Team have more than one timeline
Hi.
I created more than one timeline to track different types of work going on at the same time, but it is for the same team. I also, did it this way so that I could have more than one current iteration.
Is there a way to assign more than one timeline to a team? So far, I've only seen that you can assign one per team. The others get assigned to the Project level? This seems to be causing problems with creating iteration plans.
Any info would be helpful.
Thanks in advance!
I created more than one timeline to track different types of work going on at the same time, but it is for the same team. I also, did it this way so that I could have more than one current iteration.
Is there a way to assign more than one timeline to a team? So far, I've only seen that you can assign one per team. The others get assigned to the Project level? This seems to be causing problems with creating iteration plans.
Any info would be helpful.
Thanks in advance!
9 answers
You cannot assign more than one timeline to a team. The intention is that you should create separate team areas for the different work. For example, if you want to have multiple timelines in a project, you might have a "main" timeline and a maintenance release timeline. In this case, you would create a new team area for the team that is doing maintenance work. This allows you to have different members (though they might be the same as the other team), and different process rules for the maintenance team.
---
Ryan Manwiller
Jazz Team
---
Ryan Manwiller
Jazz Team
Hi.
We just finished a release, and I was organizing RTC to get ready for new development. Is there a way to archive iterations so that they aren't deleted, but don't show in the Planned For dropdown, and All Plans view?
Also, is there any way to customize the All Plans view?
Thanks in advance!!
We just finished a release, and I was organizing RTC to get ready for new development. Is there a way to archive iterations so that they aren't deleted, but don't show in the Planned For dropdown, and All Plans view?
Also, is there any way to customize the All Plans view?
Thanks in advance!!
You can archive iterations. I don't know whether this removes them from the Planned For or All Plans view.
Beware that you cannot un-archive an iteration once you archive it.
Go to the project area editor in the eclipse client. On the Overview page, go to the Timelines section, right-click the iteration -> Delete. This is actually an archive. You can see the archived iterations by clicking the filter button for "Show Archived" in the Timelines section header.
---
Ryan Manwiller
Jazz Team
Beware that you cannot un-archive an iteration once you archive it.
Go to the project area editor in the eclipse client. On the Overview page, go to the Timelines section, right-click the iteration -> Delete. This is actually an archive. You can see the archived iterations by clicking the filter button for "Show Archived" in the Timelines section header.
---
Ryan Manwiller
Jazz Team
You cannot assign more than one timeline to a team. The intention is that you should create separate team areas for the different work. For example, if you want to have multiple timelines in a project, you might have a "main" timeline and a maintenance release timeline. In this case, you would create a new team area for the team that is doing maintenance work. This allows you to have different members (though they might be the same as the other team), and different process rules for the maintenance team.
---
Ryan Manwiller
Jazz Team
When creating more than one timeline in a project I notice that there is a tick-box for setting the timeline as the project timeline. What is the purpose of this setting? We generally develop four products in one project concurrently - each with its own timeline and none of the four set to be the project timeline. Is this a no-no in RTC?
We are using the Scrum process template.
Cheers
You can use the project area itself as the process area for a team (and
create plans for the project area). To do so, you would need to know
what the timeline of the project area itself is (to know what is the
"current" iteration, for example). If a project area has only one
timeline, then that is the timeline for the project area. But if the
project area has more than one timeline, you have to specify which is
the timeline for a team working directly in the project area.
Cheers,
Geoff
bmiller wrote:
create plans for the project area). To do so, you would need to know
what the timeline of the project area itself is (to know what is the
"current" iteration, for example). If a project area has only one
timeline, then that is the timeline for the project area. But if the
project area has more than one timeline, you have to specify which is
the timeline for a team working directly in the project area.
Cheers,
Geoff
bmiller wrote:
ryanmanwrote:
You cannot assign more than one timeline to a team. The intention is
that you should create separate team areas for the different work.
For example, if you want to have multiple timelines in a project, you
might have a "main" timeline and a maintenance release
timeline. In this case, you would create a new team area for the team
that is doing maintenance work. This allows you to have different
members (though they might be the same as the other team), and
different process rules for the maintenance team.
---
Ryan Manwiller
Jazz Team
When creating more than one timeline in a project I notice that there
is a tick-box for setting the timeline as the project timeline. What
is the purpose of this setting? We generally develop four products in
one project concurrently - each with its own timeline and none of the
four set to be the project timeline. Is this a no-no in RTC?
We are using the Scrum process template.
Cheers
If a project area has only one timeline, then that is the timeline for
the project area. But if the project area has more than one timeline,
you have to specify which is the timeline for a team working directly
in the project area.
Thanks, Geoff, but this isn't quite accurate. The number of timelines
(one vs. many) doesn't matter. The question is just whether or not a
project timeline is set. If I may, here's a correction:
If a project area has a project timeline, then that is the timeline for
the project area. All team areas belong to the project timeline unless
they are explicitly assigned to another timeline.
--
Jared Burns
Jazz Process Team
You can use the project area itself as the process area for a team (and
create plans for the project area). To do so, you would need to know
what the timeline of the project area itself is (to know what is the
"current" iteration, for example). If a project area has only one
timeline, then that is the timeline for the project area. But if the
project area has more than one timeline, you have to specify which is
the timeline for a team working directly in the project area.
Cheers,
Geoff
Thanks Geoff. We are using multiple teams to keep things reasonably organized and to allow for slightly differing processes. It sounds like we are OK with timelines for for the teams/products and ignoring the project timeline. Did I follow you correctly?
Cheers
Yes, if all of your teams are assigned to team areas (i.e., no team is
working directly in the project area), then there is no need to set the
project area timeline.
Cheers,
Geoff
bmiller wrote:
working directly in the project area), then there is no need to set the
project area timeline.
Cheers,
Geoff
bmiller wrote:
gmclemmwrote:
You can use the project area itself as the process area for a team
(and
create plans for the project area). To do so, you would need to
know
what the timeline of the project area itself is (to know what is the
"current" iteration, for example). If a project area has
only one
timeline, then that is the timeline for the project area. But if
the
project area has more than one timeline, you have to specify which
is
the timeline for a team working directly in the project area.
Cheers,
Geoff
Thanks Geoff. We are using multiple teams to keep things reasonably
organized and to allow for slightly differing processes. It sounds
like we are OK with timelines for for the teams/products and ignoring
the project timeline. Did I follow you correctly?
Cheers
Thanks for the clarification, Jared.
And I'm glad I was wrong ... the way it actually works is better than
the way I described it (:-).
Cheers,
Geoff
Jared Burns wrote:
And I'm glad I was wrong ... the way it actually works is better than
the way I described it (:-).
Cheers,
Geoff
Jared Burns wrote:
If a project area has only one timeline, then that is the timeline for
the project area. But if the project area has more than one timeline,
you have to specify which is the timeline for a team working directly
in the project area.
Thanks, Geoff, but this isn't quite accurate. The number of timelines
(one vs. many) doesn't matter. The question is just whether or not a
project timeline is set. If I may, here's a correction:
If a project area has a project timeline, then that is the timeline for
the project area. All team areas belong to the project timeline unless
they are explicitly assigned to another timeline.