Skip to main content

What does UltimPM take into account when scheduling ?

Constraints​

UltimPM will try and find the best sequence of tasks that will fit the following requirements :

  • The earliest a task can start is the current date
  • Each task needs to finish before its drop dead date
    • If UltimPM can’t find a solution where all tasks end before their drop dead date, it will try and prioritize those tasks that have a higher priority.
  • Each task needs to be assigned a resource which skills match the skill assigned to the task
  • Each task needs to end before each of its downstream dependencies starts.
    • Note that only finish to start type dependencies are supported by UltimPM.
  • If a resource that’s assigned to a task is not available during the task’s execution window, the task’s duration is stretched out as to overlap those unavailability dates.
  • The amount of time between the start date of the earliest task and the end date of the latest task is as short as possible

Starting point​

When you initiate the planning of a project with UltimPM, it will:

  • Reset all the start dates in the plan's tasks to the current date.
  • Reset all the tasks' resources assignments
    • Please note here that this doesn't refer to the standard Asana "Assignee" field but rather to the custom "Assigned to" field in which ultimPM provides the label of the resource that has been assigned to a task after processing of plan has been completed.

Therefore if you launch UltimPM's scheduling several times on the same project, you will probably get different results every time.

Notes​

  • UltimPM doesn't touch subtasks. Any subtask of a task within a plan is ignored by the processing of the plan.
  • Plans can have groups and tasks within groups/sections will be planned as part of the plan as a whole, not separatly.