It's all about the answers!

Ask a question

Any quantification of project "overhead" ?


Kevin Ramer (4.5k9185200) | asked Mar 03 '10, 12:27 p.m.
I've searched the jazz for 'overhead' most deal with something other than
what I'm asking about. Let's say I have several projects in an RTC repo. What is the overhead that comes with creating a new project ? That is how much more will the database increase.

I have users who think having projects & teams is inconvenient even though their work is related.

One answer



permanent link
Geoffrey Clemm (30.1k33035) | answered Mar 03 '10, 5:23 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The physical database overhead of adding an additional project area is
minimal. So your criteria for whether or not to create additional
project areas should be based on the process semantics needed by those
teams, not by any concern of database overhead.

Cheers,
Geoff

yzwkzfn wrote:
I've searched the jazz for 'overhead' most deal with something other
than
what I'm asking about. Let's say I have several projects in an RTC
repo. What is the overhead that comes with creating a new project ?
That is how much more will the database increase.

I have users who think having projects & teams is inconvenient
even though their work is related.

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.