none
summary and chil tasks not scheduling the same way? RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I have a summary task which I linked to a predecessor, the start date came out as 14th january, as did all its children - they are all "as soon as possible".

    Given that the predecessor is a milestone and on 24th January this seemed wrong. So as a test I didn't change anything except instead of putting the predecessor on the summary task i put it on one of the children. Then that child started on 24th as I expected.

    What would cause this behaviour?

    thank you.................liz

    Thursday, October 18, 2012 1:43 PM
    |

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    OK, someone - probably me in a moment of confusion - had made the summary task manual so no wonder!

    thank you.................liz


    • Edited by lizat Thursday, October 18, 2012 1:51 PM
    Thursday, October 18, 2012 1:50 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    It is never a good practice to use the summaries as predecessors or successors (also do not assign resources, cost or work to summaries). Reasons:

    Only a task/milestone/event can be a predecessor or successor
    Summaries are just a way of organising tasks/milestones/events within the work breakdown structure
    Just because the sofware allows it doesn't mean that you must do it
    It is easy to create circular references.
    Levelling won't work
    Thursday, October 18, 2012 1:58 PM
    |