Unassigned Resources

M

Mike Mahoney

Gary/Dale

I was shocked and horrified to read paragraph 1 on page 676 of your
might tome. This explains how activity plans create work without a
resource assignment, and on checking my Data Analysis reports it is
exactly as you describe. Can you explain the logic behind this?

On a related note - have you noticed that PWA Assignment based Project
Detail views also "generate" work for tasks without an assignment
based on duration. e.g. Assignments Detail view.

regards

Mike
 
J

Jackson T. Cole

Makes sense except for the "Fixed Cost" part. I can't see calling that an
"unassigned" resource. Maybe an "unknown" material resource?

BTW, kudos on the "tome"! It will serve me well until I have time and
money for training! :>)
JTC
 
M

Mike Mahoney

   Makes sense except for the "Fixed Cost" part.  I can't see calling that an
"unassigned" resource. Maybe an "unknown" material resource?

    BTW, kudos on the "tome"! It will serve me well until I have time and
money for training!  :>)
JTC

:





- Show quoted text -

Dale

I might be missing/misunderstanding something.
If I create an activity plan I would normally expect to assign a
resource (at least a generic), if not it's because the task does not
warrant a resource - might be a procurement task taking 3 months. For
PWA to assume that 3 months involves an unassigned resource and to
inflate the data analysis reports by this "requirement" is wrong.
Proposal plans again can be created as placeholders and tasks created
to identify high level timespans. The assumption that a headcount of
1 is associated with these tasks is not a good assumption.

regards

Mike
 
G

Gary L. Chefetz [MVP]

Mike:

I'm not specifically defending the design, mind you, but it does make sense
to me when considering that the primary purpose of proposed projects and
activity plans is to create resource demand placeholders. Given the very
limited planning capabilities of proposals, it sounds to me like your
expectations are exceeding their limitations. Have you tried adding a
resource plan to a proposal instead of creating specific tasks? The resource
plan gives you greater flexibility in determining how work loading is
calculated. If your proposals are so detailed that you're down to the level
of specifying lead times on procurement tasks, you might be better served by
using the Project Client to create real projects for these.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com


Makes sense except for the "Fixed Cost" part. I can't see calling that an
"unassigned" resource. Maybe an "unknown" material resource?

BTW, kudos on the "tome"! It will serve me well until I have time and
money for training! :>)
JTC

:





- Show quoted text -

Dale

I might be missing/misunderstanding something.
If I create an activity plan I would normally expect to assign a
resource (at least a generic), if not it's because the task does not
warrant a resource - might be a procurement task taking 3 months. For
PWA to assume that 3 months involves an unassigned resource and to
inflate the data analysis reports by this "requirement" is wrong.
Proposal plans again can be created as placeholders and tasks created
to identify high level timespans. The assumption that a headcount of
1 is associated with these tasks is not a good assumption.

regards

Mike
 
M

Mike Mahoney

Mike:

I'm not specifically defending the design, mind you, but it does make sense
to me when considering that the primary purpose of proposed projects and
activity plans is to create resource demand placeholders. Given the very
limited planning capabilities of proposals, it sounds to me like your
expectations are exceeding their limitations. Have you tried adding a
resource plan to a proposal instead of creating specific tasks? The resource
plan gives you greater flexibility in determining how work loading is
calculated. If your proposals are so detailed that you're down to the level
of specifying lead times on procurement tasks, you might be better served by
using the Project Client to create real projects for these.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting:http://www.msprojectexperts.com
For Project Server FAQS:http://www.projectserverexperts.com







Dale

I might be missing/misunderstanding something.
If I create an activity plan I would normally expect to assign a
resource (at least a generic), if not it's because the task does not
warrant a resource - might be a procurement task taking 3 months.  For
PWA to assume that 3 months involves an unassigned resource and to
inflate the data analysis reports by this "requirement" is wrong.
Proposal plans again can be created as placeholders and tasks created
to identify high level timespans.  The assumption that a headcount of
1 is associated with these tasks is not a good assumption.

regards

Mike- Hide quoted text -

- Show quoted text -

Dale

I don't disagree with any of your comments but the way PWA creates in
unassigned resource in a proposal or Activity plan is a complete
surprise. Clearly a resource plan is the way to define early resource
requirements, in which case the unassigned resource generated by the
proposal plan has even less purpose. Many proposal plans might contain
single bar which simply allows you to publish a target start and a
finish date. At this stage in the process resourcing is premature. For
PWA to generate an arbitrary amount of unassigned resource serves no
purpose.

Anyway I am now forwarned and therefore forearmed thanks to your book.

regards

Mike
 
G

Gary L. Chefetz [MVP]

Mike:

Thanks for the kind words. I'm growing fond of proposals with start and end
dates, no tasks and an attached resource plan.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com


Mike:

I'm not specifically defending the design, mind you, but it does make
sense
to me when considering that the primary purpose of proposed projects and
activity plans is to create resource demand placeholders. Given the very
limited planning capabilities of proposals, it sounds to me like your
expectations are exceeding their limitations. Have you tried adding a
resource plan to a proposal instead of creating specific tasks? The
resource
plan gives you greater flexibility in determining how work loading is
calculated. If your proposals are so detailed that you're down to the
level
of specifying lead times on procurement tasks, you might be better served
by
using the Project Client to create real projects for these.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting:http://www.msprojectexperts.com
For Project Server FAQS:http://www.projectserverexperts.com







Dale

I might be missing/misunderstanding something.
If I create an activity plan I would normally expect to assign a
resource (at least a generic), if not it's because the task does not
warrant a resource - might be a procurement task taking 3 months. For
PWA to assume that 3 months involves an unassigned resource and to
inflate the data analysis reports by this "requirement" is wrong.
Proposal plans again can be created as placeholders and tasks created
to identify high level timespans. The assumption that a headcount of
1 is associated with these tasks is not a good assumption.

regards

Mike- Hide quoted text -

- Show quoted text -

Dale

I don't disagree with any of your comments but the way PWA creates in
unassigned resource in a proposal or Activity plan is a complete
surprise. Clearly a resource plan is the way to define early resource
requirements, in which case the unassigned resource generated by the
proposal plan has even less purpose. Many proposal plans might contain
single bar which simply allows you to publish a target start and a
finish date. At this stage in the process resourcing is premature. For
PWA to generate an arbitrary amount of unassigned resource serves no
purpose.

Anyway I am now forwarned and therefore forearmed thanks to your book.

regards

Mike
 
Top