J
Javier
Quick question,
Does a restriction like "finish no later than" works in a summary task?
Thanks
Does a restriction like "finish no later than" works in a summary task?
Thanks
M
Mike Glen
Hi Javier,
Welcome to this Microsoft Project newsgroup
Well....Project allows the entry. However you have to be aware that such a
constraint does not mean that the tasks will finish no later than, just that
that is what you want the schedule to do. I would continue to use As soon
as possible as this will give you the greatest flexibility, as any other
constraint will cause a reduction in flexibility. Instead, I would use a
Deadline date as an aiming point. If the plan schedule indicates a later
finish than that, then an indicator will show in the Indicators column,
whence you will have to revise your schedule to meet the deadline.
FAQs, companion products and other useful Project information can be seen at
this web address: http://project.mvps.org/faqs.htm
Hope this helps - please let us know how you get on
Mike Glen
MS Project MVP
See http://tinyurl.com/2xbhc for my free Project Tutorials
Welcome to this Microsoft Project newsgroup
Well....Project allows the entry. However you have to be aware that such a
constraint does not mean that the tasks will finish no later than, just that
that is what you want the schedule to do. I would continue to use As soon
as possible as this will give you the greatest flexibility, as any other
constraint will cause a reduction in flexibility. Instead, I would use a
Deadline date as an aiming point. If the plan schedule indicates a later
finish than that, then an indicator will show in the Indicators column,
whence you will have to revise your schedule to meet the deadline.
FAQs, companion products and other useful Project information can be seen at
this web address: http://project.mvps.org/faqs.htm
Hope this helps - please let us know how you get on
Mike Glen
MS Project MVP
See http://tinyurl.com/2xbhc for my free Project Tutorials
J
Javier
Thanks for the answers. I have tested it and it does work. I have a program
where some resources are working in different projects and some of them
cannot be finished later than a certain date. I tested by reducing the % of
resource available and leveling the entire program and the projects (summary
tasks) with "finish no later" restriction were delayed up to this date.
where some resources are working in different projects and some of them
cannot be finished later than a certain date. I tested by reducing the % of
resource available and leveling the entire program and the projects (summary
tasks) with "finish no later" restriction were delayed up to this date.
M
Mike Glen
You're welcome, Javier
Mike Glen
MS Project MVP
See http://tinyurl.com/2xbhc for my free Project Tutorials
Mike Glen
MS Project MVP
See http://tinyurl.com/2xbhc for my free Project Tutorials
S
Steve House
But remember that the schedule in Project is not just a document to
illustrate your requirements. It's actually a computational model designed
to help your figure out just how you need to organize the workflow and
assign the resources in order to successfully meet those requirements. The
dates task will happen are driven by physical processes such as when their
predecessors are complete and when the resources will be available to do
them - they're not just arbitrarily assigned in order to meet a certain
deadline. Project's schedule models those processes. A "finish no later
than" constraint will always show the task in question finishing on-time,
even if it's actually physically impossible for it to happen that way. In
fact, it will even show the constrained task finishing on-time even if its
predecessors haven't started yet! For the scheduling engine to have its
greatest benefit, you need to let it show you what dates you'll hit if you
attempt to work with a given workflow. If you let Project freely calculate
where the task will go and it insists on putting it too late, you know that
if you go with that particular workflow the project will fail. It's telling
you that you need to redesign the workflow and resource assignments until
the computed date fall within your required target dates. The proper way to
illustrate the target date is through a deadline entry. That will mark the
date you need to hit in the schedule and show you whether your present trial
workflow is going to achieve it or not.
illustrate your requirements. It's actually a computational model designed
to help your figure out just how you need to organize the workflow and
assign the resources in order to successfully meet those requirements. The
dates task will happen are driven by physical processes such as when their
predecessors are complete and when the resources will be available to do
them - they're not just arbitrarily assigned in order to meet a certain
deadline. Project's schedule models those processes. A "finish no later
than" constraint will always show the task in question finishing on-time,
even if it's actually physically impossible for it to happen that way. In
fact, it will even show the constrained task finishing on-time even if its
predecessors haven't started yet! For the scheduling engine to have its
greatest benefit, you need to let it show you what dates you'll hit if you
attempt to work with a given workflow. If you let Project freely calculate
where the task will go and it insists on putting it too late, you know that
if you go with that particular workflow the project will fail. It's telling
you that you need to redesign the workflow and resource assignments until
the computed date fall within your required target dates. The proper way to
illustrate the target date is through a deadline entry. That will mark the
date you need to hit in the schedule and show you whether your present trial
workflow is going to achieve it or not.