Re: Schedule Calculation - Why don't unstarted tasks move to the r

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hello Vic,

The "reschedule uncompleted tasks" command will place a start no
earlier than constraint on any task which was scheduled to start and
was moved by the command. I understand the desire to keep constraints
to a minimum, but in this case, the constraints are a necessary
component to keep the project close to reality. I suppose you could
leave the tasks where they were originally scheduled (no constraints)
and just wait to update the status by supply actual start dates and
task progress updates. However, I personally find that to be more
confusing -- why have a task showing scheduled in the past when I know
that it hasn't been started as scheduled. Keeping the project up to
date also gives a much clearer picture about the possible impacts of
delays. You comment that you have many unstarted tasks -- without
moving the tasks to the new status date, how can you predict the
revised finish dates of both the tasks and the entire project?

I hope this helps. Let us know how you get along.

Julie
Project MVP

Visit http://project.mvps.org/ for the FAQs and additional information
about Microsoft Project



"Vic" <Vic@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B01D3D19-A66B-44BA-AA66-F0A7DD7BBE05@xxxxxxxxxxxxxxxx

Is there a way to do it so it doesn't set a constraint on the task?
Those
little icons on the left let me know I have a constraint that needs
to be
looked at (I try to keep them to a minimum). This sets all
unstarted tasks
that way, so I have so many on my plan. Any thoughts?
--
Vic


"JulieS" wrote:

Hi John,

You're most welcome for the assist and thanks for the feedback.
Julie
Project MVP
"John Garay - DecisionEdge" <info@xxxxxxxxxxxxxxxx> wrote in
message
news:AF5B88EA-723A-43BB-8651-B000E3AFB3C0@xxxxxxxxxxxxxxxx
Julie and Joe -

Thanks for the hint - That did the trick.
I found the options dialog on my own, but now I also know about
this
tracking update dialog...

Regards,
John Garay
DecisionEdge, Inc.

"Joe" <joeg10@xxxxxxxxxxx> wrote in message
news:eYHH1z7JIHA.3356@xxxxxxxxxxxxxxxxxxxxxxx
Use Tools/Tracking/Update Project. Select the second radio
button
"Reschedule uncompleted work to start after"

That's the way MSP works.


"John Garay - DecisionEdge" <info@xxxxxxxxxxxxxxxx> wrote in
message
news:4A5BCB17-388A-4316-8341-3E1FC22C64E5@xxxxxxxxxxxxxxxx
I would appreciate some help understanding the way MSP works as
I
transition from Primavera:

Why are unfinished tasks not moved to the right of the project
status date?
There's no way a task can happen to the left - so why doesn't
MSP
push an unstarted task forward to the project status date?

Here's the scenario:
Project Current Date is today: 15 Nov 07
Project Status Date is today: 15 Nov 07
Project Start Date is 2 August 2007

When I add a new task (no constraints, no predecessors), it is
set
to the Project Start Date (I know this is a Schedule Option).
If I
force a schedule update, the new task just sits at the project
start. I would expect it to instead move to the project status
date, the soonest it can actually happen. (I worked at
Primavera
for 12+ years - that's what I am used to seeing in Primavera)

How can I get the dates of unstarted tasks to the status date?

Thanks in advance!

Regards,
John Garay
DecisionEdge, Inc.

PS - I didn't see this in the mvps FAQ







.

Relevant Pages

  • Re: Proper Leveling Techniques - Rescheduling to start later
    ... Start and Finish are what your schedule calls ... Baseline Start and Finish are your original starting plan ... otherwise to force the tasks to end up on certain dates - leveling has ... I don't know why you're so adament againt using SNET constraints in any ...
    (microsoft.public.project)
  • Re: Hold out on entering dates?
    ... So I'd decompose your schedule down to the point that if A & B can indeed be assembled together and set aside to await C's arrival, that module constitutes a discrete deliverable and thus "Assemble A&B" would be one task while "Join Module AB with C" would be an entirely separate task. ... Before the first of those two task's I'd enter 2 milestones, "Receive Parts A" with an SNET of 1/1 and "Receive Parts B" with an SNET of 2/1. ... Assembly task 1's schedule start would be calculated from those milestones and its finish by its duration but it would have no constraints, Project freely calculating its dates without any input from us. ...
    (microsoft.public.project)
  • Re: Proper Leveling Techniques - Rescheduling to start later
    ... You don't tell it the schedule, ... >> It is NEVER appropriate to use leveling delays to bring forward work or>> otherwise to force the tasks to end up on certain dates - leveling has>> nothing to do with that. ... The only time leveling delays should be>> anything except blank is when the resource leveling tool has introduced>> them to resolve resource overallocations. ... >> I don't know why you're so adament againt using SNET constraints in any>> situation. ...
    (microsoft.public.project)
  • Re: Building a schedule
    ... where you do need to establish constraints and that is why Project ... The boss may have even said "fidgeting the widgets MUST ... availability of the resources who will actually do the work and then it ... calculates the schedule that is possible under those conditions. ...
    (microsoft.public.project)
  • Re: Proper Leveling Techniques - Rescheduling to start later
    ... You don't tell it the schedule, ... The only time leveling delays should be ... I don't know why you're so adament againt using SNET constraints in any ... Project tool apply an SNET constraint is perfectly ok - that's what ...
    (microsoft.public.project)