Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Project setup with multiple teams/timelines

Hello,
We're looking to implement RTC for our internal development teams. We're looking for guidance on best practices with the project area, team area and especially timeline setup.

In a nutshell this is what we need:
- Each team has unique but related timelines.
- All of these timelines will tie into an overall timeline.

What is the best way to structure and manage these timelines? As we all know, the introduction of multiple timelines in a project adds complexity. What is the best way to setup this up in RTC?
I'll appreciate any guidance and previous experiences one could share in this area.
Thank you in advance.

1 vote



5 answers

Permanent link
Thanks for the links, it explains well the RTC concepts.
However, our concerns are based on the presentation to the user of multiple timelines and the proper allocation and distribution of workitems to the "correct" timelines when submitted. As well there seem to be a bit of confusion of how to make sure work-items and relationships between the timelines make sense. So in other words how to make sure that the overall project timeline gets the right feeds of information from the "sub-timelines". Ok, sub-timelines don't exist in RTC but from an organizational perspectives this is what they are.
Any guidance and experiences along those lines would be appreciated.
Thanks.

1 vote


Permanent link
I would encourage you to minimize the number of timelines, since
currently, you cannot have a single plan that spans iterations from more
than one timeline.

Work item 94056 requests the ability to do so ... please feel free to
add a comment to that work item to indicate your interest/support.

Cheers,
Geoff

On 6/22/2011 1:53 PM, zachary wrote:
Thanks for the links, it explains well the RTC concepts.
However, our concerns are based on the presentation to the user of
multiple timelines and the proper allocation and distribution of
workitems to the "correct" timelines when submitted. As
well there seem to be a bit of confusion of how to make sure
work-items and relationships between the timelines make sense. So in
other words how to make sure that the overall project timeline gets
the right feeds of information from the "sub-timelines".
Ok, sub-timelines don't exist in RTC but from an organizational
perspectives this is what they are.
Any guidance and experiences along those lines would be appreciated.
Thanks.

1 vote


Permanent link
Here is a doc you might be interested in:
https://jazz.net/library/article/542#Adopting_Plans

0 votes


Permanent link
One more doc: https://jazz.net/library/article/137

0 votes


Permanent link
Hi There,

My request is very similar to Zach's, to reword it, I'd like the ability for :
a) Multiple Agile scrum teams to exist in the same project area, each having their own timeline (as their iteration start and end dates might not coincide with each other), however all Agile teams have the same Release start and end dates
b) Ability roll up reporting across Releases for ALL Agile teams

The only way i can imagine this happening is to enable 'Sub Timelines' (this is currently not possible) so that story points can be rolled up across ALL Scrum Teams that each have their own sub timelines, to a 'Master Timeline' , from which the rolled up reporting view is produced.

Can anyone suggest any other workaround to get a rolled up release reporting view across scrum teams that each have their own iteration cadences?

Thanks,
KH

0 votes

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Jun 21 '11, 10:56 a.m.

Question was seen: 6,409 times

Last updated: Dec 15 '13, 9:01 p.m.

Confirmation Cancel Confirm