none
Rescheduling on a task on a "backward" Project - Project Server 2010 RRS feed

  • Question

  • Hi everybody,

    We have strange behaviour with an 'auto' rescheduling on tasks.

    The project is scheduling 'backward', from the finish date and the tasks are 'late as possible'.  The end of the project is on 30.06.13

    The activities on the project have begun and ressources started to fill the time up. We don't use the timesheet part of Project server. The State Date (not sure of the translation) of the project is on 28.01.13.

    The situation :

    Task A : start 04.03.13  End 06.03.13  as late as possible

    Task B : start 24.12.12  End 24.12.12  as late as possible

    Task C : start 07.03.13 End 08.03.13  as late as possible / task A is predecessor of task C

    The ressource completed Task B and Task C at 100%. It means the Task C ended earlier than scheduled.

    The problem is that now the Task A get : Start 26.06.13  End 28.06.13

    We don't understand why there is reschedule, automatically. In a 'standard' Project, scheduling from Start date, there is no automatic reschedule. The Task A is late, and we can see it and the resource in charge too. But we don't want this task on June ! March is the right term.

    Can you explain why there is a reschedule ? and how to avoid it ?

    Many thanks in advance, best regards

    Anne


    Anne Renaud Project Manager PMP Vision 2 Action SA Switzerland


    • Edited by AnneV2a.ch Monday, January 28, 2013 5:19 PM
    Monday, January 28, 2013 5:15 PM

Answers

  • Hi Graham,

    I think that, eventhough there is a dependecy between the tasks, the fact that Task C is completed before Task A makes the depency broken and then the Task A is re-scheduled as a 'unique' task and it's "pushed" to the end of the project.

    What is annoying is not that the task is recalculated and push to the end, but that it is done automaticaly. Which means, if the resource checks it's weekly tasks it would not find it and miss the real delay.

    Anyway, now we know how Project reacts. The next projects won't be scheduled as this, especially as the customer is not able to ensure a regular timeinput from his resources.

    Many thanks for your support

    Have a nice week-end

    Anne


    Anne Renaud Project Manager PMP Vision 2 Action SA Switzerland

    • Marked as answer by AnneV2a.ch Friday, February 1, 2013 2:05 PM
    Friday, February 1, 2013 2:04 PM

All replies

  • Anne, there are a couple of things that seem odd with the project.

    • Why is it scheduled from the finish date? This means that tasks will be scheduled as late as possible, there is zero slack on all unconstrained tasks and the project manager has a really tough job.
    • If Task A is a predecessor of Task C, how come Task C is now complete and Task A is not started?
    • If the dependency between Tasks A and C no longer applies, then the as late as possible constraint type on Task A would cause it to be scheduled immediately before the end of project date.

    In a conventional project with all tasks as soon as possible, Task A would be rescheduled according to whatever rules you apply - probably starting immediately after the status date (28 January).

    Graham

    Tuesday, January 29, 2013 3:42 AM
  • Hello Graham,

    I agree with you, it could seem a very odd project, but it is not a "real" project. In that case, we use project to get a kind of monitoring over operational tasks on a very well know process in the organization.

    Project is use to provide scheduled tasks to each group or people and spread the taks until June. That's why we choose to plan 'Backward'.

    For this case, Task C and Task A are linked. But the person in charge of Task A did not complete either the task or the time in Project server.

    I can't understand why Project is rescheduling automatically the Task A date as we did not recalculate or advance the task until the state date. Is it a specific behaviour because it is a 'backward' Project ?

    Anne


    Anne Renaud Project Manager PMP Vision 2 Action SA Switzerland

    Tuesday, January 29, 2013 2:39 PM
  • Anne, I can't replicate your case exactly, but if there is no dependency between tasks A and C and task A is scheduled As Late As Possible (as in a backward project) - then yes, I would expect to see what you get. Task A scheduled immediately before the project end date.

    Graham

    Tuesday, January 29, 2013 3:42 PM
  • Hi Graham,

    I think that, eventhough there is a dependecy between the tasks, the fact that Task C is completed before Task A makes the depency broken and then the Task A is re-scheduled as a 'unique' task and it's "pushed" to the end of the project.

    What is annoying is not that the task is recalculated and push to the end, but that it is done automaticaly. Which means, if the resource checks it's weekly tasks it would not find it and miss the real delay.

    Anyway, now we know how Project reacts. The next projects won't be scheduled as this, especially as the customer is not able to ensure a regular timeinput from his resources.

    Many thanks for your support

    Have a nice week-end

    Anne


    Anne Renaud Project Manager PMP Vision 2 Action SA Switzerland

    • Marked as answer by AnneV2a.ch Friday, February 1, 2013 2:05 PM
    Friday, February 1, 2013 2:04 PM