It's all about the answers!

Ask a question

Best Practice for Timelines with Formal Project Mgmt Process


Todd Goldstein (76119) | asked Jun 22 '11, 8:28 a.m.
retagged Jun 17 '13, 5:05 p.m. by Michael Prentice (622913)
I am using RTC with the Formal Project Management Process Template and wanted to know the best practice for creating timelines. This implementation is for traditional non-product development projects.

The project(s) my team work on differ however from a management point of view, we review information on a monthly, quarterly, and yearly basis.

I'm wondering if it makes more sense to leverage the tree structure and create the following:

Level 1 - 2011
Level 2 - Q1, Q2, Q3, Q4
Level 3 - Jan, Feb, Mar...Dec

OR should I flatten everything and have 1 level? How much will this impact the Plan view?

One answer



permanent link
Geoffrey Clemm (30.1k33035) | answered Jun 22 '11, 6:20 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I'd suggest the former approach, i.e. leverage the tree structure. This
allows you to plan at any of the three levels (when you create a plan,
you would specify at what level you want the plan to be).

Cheers,
Geoff

On 6/22/2011 8:38 AM, tgoldstein wrote:
I am using RTC with the Formal Project Management Process Template and
wanted to know the best practice for creating timelines. This
implementation is for traditional non-product development projects.


The project(s) my team work on differ however from a management point
of view, we review information on a monthly, quarterly, and yearly
basis.

I'm wondering if it makes more sense to leverage the tree structure
and create the following:

Level 1 - 2011
Level 2 - Q1, Q2, Q3, Q4
Level 3 - Jan, Feb, Mar...Dec

OR should I flatten everything and have 1 level? How much will this
impact the Plan view?

Your answer


Register or 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.