Re: 2003 Admin Project Limitations????
From: Randy (Randy_at_discussions.microsoft.com)
Date: 08/19/04
- Next message: Karl Kill: "RE: Pre-filtered 'Build Team from Enterprise'"
- Previous message: Dale Howard [MVP]: "Re: 2003 Admin Project Limitations????"
- In reply to: Dale Howard [MVP]: "Re: 2003 Admin Project Limitations????"
- Next in thread: Randy: "Re: 2003 Admin Project Limitations????"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 19 Aug 2004 07:45:02 -0700
Dale,
Excuse the duplicate message I left. They system hiccupped and said my
reply would have to be resubmitted (apparently not).
Anyway, I attended a 2003 PM Training Class given by Quantum PM. In the
training material two of the special characteristics of admin projects that
were listed are:
1) limit of 50 resources per task
2) can assign only 500 resources per project (ie: 50 resources per each task
with a limit of 10 tasks to a project schedule)
When I questioned the instructor she did not have any further information
and suggested I contact one of her associates. I'm waiting to here back.
I've found no other documentation regarding limitations anywhere.
Randy
"Dale Howard [MVP]" wrote:
> Randy --
>
> I'm not aware of any such limitations, but I could be wrong. Where did you
> get the information about limitations?
>
> --
> Dale A. Howard [MVP]
> Enterprise Project Trainer/Consultant
> http://www.msprojectexperts.com
> "We wrote the book on Project Server"
>
>
> "Randy" <Randy@discussions.microsoft.com> wrote in message
> news:BF571A06-7D98-4812-914F-9589570C425C@microsoft.com...
> > Dale,
> >
> > Actually, I would prefer to have each team have their own admin project
> but
> > we are not sure the maturity level is where it needs to be yet (as far as
> > methodologies, work flow, etc...). I will revisit this.
> >
> > Do admin projects have limitations as far as the number of resources and
> > tasks go?
> >
> > Thanks!
> >
> > Randy
> >
> > "Dale Howard [MVP]" wrote:
> >
> > > Randy --
> > >
> > > I would recommend that you seriously reconsider assigning all 800
> resources
> > > to each task. I beieve that such a project would be an administrative
> > > nightmare to manage! Instead, I would recommend that you use an
> alternate
> > > approach, such as creating a separate administrative project for each
> team,
> > > department, business unit, or something like that. If you need to view
> the
> > > total information across all of the administrative projects, you could
> > > create a temporary master project containing each administrative project
> as
> > > a subproject. Just a thought.
> > >
> > > --
> > > Dale A. Howard [MVP]
> > > Enterprise Project Trainer/Consultant
> > > http://www.msprojectexperts.com
> > > "We wrote the book on Project Server"
> > >
> > >
> > > "Randy" <Randy@discussions.microsoft.com> wrote in message
> > > news:1D970822-600A-4BF0-BE6B-4D51649F67C4@microsoft.com...
> > > > I'm about to implement an Admin Project and was just told that you can
> > > only
> > > > assign 500 resources per project (for instance 50 resources on 10
> tasks).
> > > I
> > > > have not found this documented anywhere and am looking for
> confirmation.
> > > I
> > > > was hoping to set up one admin project with approx. 8 tasks and assign
> all
> > > > 800 resources to each task. Any suggestions would be greatly
> appreciated.
> > > >
> > > > Thanks!
> > > >
> > > > Randy
> > >
> > >
> > >
>
>
>
- Next message: Karl Kill: "RE: Pre-filtered 'Build Team from Enterprise'"
- Previous message: Dale Howard [MVP]: "Re: 2003 Admin Project Limitations????"
- In reply to: Dale Howard [MVP]: "Re: 2003 Admin Project Limitations????"
- Next in thread: Randy: "Re: 2003 Admin Project Limitations????"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
