none
Microsoft Project plan scheduling RRS feed

  • Question

  • 1.)    Which of the following statement is false in the context of scheduling with MICROSOFT PROJECT?

    a.)     You cannot schedule from the project end date backwards.

    b.)    Recurring tasks will have hardcoded dates

    c.)     Partial resource allocation on a task is not possible

    d.)    Task calendar override resource calendars

    I think "d" option is false, could anyone please verify this. Thanks

    Wednesday, November 29, 2017 12:47 AM

Answers

  • Sandy PM,

    a.) False, Project allows scheduling from the Project finish date, but, doing so normally creates havoc.

    b.) If by "hardcoded dates" you mean dates with a constraint, then yes. But, normally "hardcoded dates" are must-start-on and must-finish-on. The "start-no-earlier-than", (which is applied when a recurring task is created), or a "no-later-than" are considered soft constraints. So under the normal definition, the answer is "false"

    c.) False, resources can be assigned at any level on a task (e.g. 1% to 100%)

    d.) True or false depending on the setting of the option "scheduling ignores resource calendars" on the Task Information window.

    Was this a pop quiz? How did I do?

    John



    Wednesday, November 29, 2017 1:46 AM
  • a) In project Information you can set for schedule from the finish date, and this will mean that all new tasks will be set to ALAP. This will take effect from when you make the setting, which could be right at the start before you have any tasks, or after you already have some tasks listed.

    If you start off with the default setting which is schedule from the start, all new tasks are ASAP. Then if you change the setting, all new tasks will be ALAP. This will leave you with a mix of ASAP and ALAP tasks. This can be achieved at any time anyway, without changing the setting in project information, simply by changing the date constraint in task information, advanced. You could also insert the type column into the current (entry) table, and edit the property there.

    Scheduling forwards from the start date and making all tasks ASAP (by default) is consistent with the critical path method, and many benefits derive from adopting and using the critical path method.

    Scheduling backwards from the finish date and making all tasks or any tasks ALAP (by default or by editing) is definitely not consistent with the critical path method, and is an abomination.

    Except for some very rare and unusual possible exceptional situations for special reasons, no one who knows what they are doing would do it.

    b), c), d) can easily be tested. Generally, define "hardcoded", no, no.

    What is "verify"? Do you mean test it or do you mean get someone else's opinion?

    Wednesday, November 29, 2017 4:21 AM

All replies

  • Sandy PM,

    a.) False, Project allows scheduling from the Project finish date, but, doing so normally creates havoc.

    b.) If by "hardcoded dates" you mean dates with a constraint, then yes. But, normally "hardcoded dates" are must-start-on and must-finish-on. The "start-no-earlier-than", (which is applied when a recurring task is created), or a "no-later-than" are considered soft constraints. So under the normal definition, the answer is "false"

    c.) False, resources can be assigned at any level on a task (e.g. 1% to 100%)

    d.) True or false depending on the setting of the option "scheduling ignores resource calendars" on the Task Information window.

    Was this a pop quiz? How did I do?

    John



    Wednesday, November 29, 2017 1:46 AM
  • a) In project Information you can set for schedule from the finish date, and this will mean that all new tasks will be set to ALAP. This will take effect from when you make the setting, which could be right at the start before you have any tasks, or after you already have some tasks listed.

    If you start off with the default setting which is schedule from the start, all new tasks are ASAP. Then if you change the setting, all new tasks will be ALAP. This will leave you with a mix of ASAP and ALAP tasks. This can be achieved at any time anyway, without changing the setting in project information, simply by changing the date constraint in task information, advanced. You could also insert the type column into the current (entry) table, and edit the property there.

    Scheduling forwards from the start date and making all tasks ASAP (by default) is consistent with the critical path method, and many benefits derive from adopting and using the critical path method.

    Scheduling backwards from the finish date and making all tasks or any tasks ALAP (by default or by editing) is definitely not consistent with the critical path method, and is an abomination.

    Except for some very rare and unusual possible exceptional situations for special reasons, no one who knows what they are doing would do it.

    b), c), d) can easily be tested. Generally, define "hardcoded", no, no.

    What is "verify"? Do you mean test it or do you mean get someone else's opinion?

    Wednesday, November 29, 2017 4:21 AM