Any quantification of project "overhead" ?
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.
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
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:
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.