P
Peter
I'm looking for references, either to printed documentation or hard-won
personal experience, for tips on setting up Project in a company. We
have several different departments with different supervisors, reporting
structures, etc.
I'm working through how to set up our processes surrounding the use of
the software, and the software itself where relevant, to accomodate our
organization.
Here's one specific example: I set up an admin project, and added
resources. Then I had one of my colleagues put in some vacation time,
and I got an email asking me to approve changes to the project tasks.
I assume this is because I created the project in the first place, but
can this be changed? Is there a way to customize reporting structures?
Rather than ask an endless series of questions, I hope someone can point
me to a good reference I can read before I really start trying to roll
this out to our users.
I hope that's coherent enough for someone to help. If not, I'll try to
clarify.
I'm looking for the 50,000 foot view, in short.
Thanks in advance.
personal experience, for tips on setting up Project in a company. We
have several different departments with different supervisors, reporting
structures, etc.
I'm working through how to set up our processes surrounding the use of
the software, and the software itself where relevant, to accomodate our
organization.
Here's one specific example: I set up an admin project, and added
resources. Then I had one of my colleagues put in some vacation time,
and I got an email asking me to approve changes to the project tasks.
I assume this is because I created the project in the first place, but
can this be changed? Is there a way to customize reporting structures?
Rather than ask an endless series of questions, I hope someone can point
me to a good reference I can read before I really start trying to roll
this out to our users.
I hope that's coherent enough for someone to help. If not, I'll try to
clarify.
I'm looking for the 50,000 foot view, in short.Thanks in advance.