Project Scheduler Update (Definition of ASAP)
This article describes the scheduling behavior of work that is set to "As Soon As Possible" (ASAP). All of the examples below assume that there are no dependencies on the ASAP item and that today is June 20th, 2013.
For a stand alone ASAP project item
The project will start "today". That is when the scheduler runs it will set the start date to today's date.
For an ASAP sub-project item under a higher level project in the work tree
The project will start on the date of the project that is highest in the work tree. In other words, the ASAP date is being constrained by the top level project. The example shows one sub-project under a project starting in the future. The second example is under a project starting in the past.
For an ASAP work item under a project
The start date of the work item will be the start date of its parent item. This could be the project itself, a phase, or a summary item. In other words, the ASAP date is being constrained by the start date of its parent. The picture above shows several cases of this.
For an ASAP work item not under a project
The start date will be "today"
For an ASAP item with children (organizations, projects, phases, summary tasks, etc.)
The parent item will start on the earliest date of its children. In other words, the ASAP date is being constrained by the dates of its children. It should be noted that this situation can constrain the ASAP date of a stand-alone ASAP project to be different than "today". This happens if I force one of its children to start earlier or later than today. Then the ASAP date of the project becomes constrained by its children.