Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>After some further experimentation, I've found a partial solution for my own question. If you:</p> <ul> <li>assign a person to each task</li> <li>specify in the Advanced tab of the Task Information panel that <em>all</em> tasks should (select all your tasks and click the Task Info button to update these properties for all tasks): <ol> <li>use a calendar (called "standard" in my project file)</li> <li><em>not</em> ignore resource calendars when scheduling</li> <li>have a constraint of As Soon As Possible (which is the default, I believe)</li> </ol></li> <li>Choose Level Resources from the Tools menu, and specify: <ol> <li>Look for overallocations on a Hour by Hour basis</li> <li>a leveling order of "Priority, Standard" (which rolls in the relative Priority values for each task you've defined when setting the schedule)</li> </ol></li> </ul> <p>Click "Level Now" in that leveling resources dialog, and all of the tasks should be rescheduled so that they're not running concurrently, and that no one is "overscheduled".</p> <p>You can ostensibly have Project automatically reschedule things as tasks are added, edited, etc., but I suspect that would result in chaos, as there's nothing about the resource leveling process that makes me think it's "stable" (e.g. that two levelings performed back-to-back wouldn't yield the same schedule).</p> <p>It would be nice if Project would "fully allocate" whatever people you have configured, so that you don't have to assign people to tasks just to have those tasks scheduled in a way that is consistent, if not correct. Any thoughts on that front would be most welcome.</p> <p> That seems (and feels!) like a lot of work, but I think the result is relatively decent -- a super-high-level view of a project that allows for a high degree of day to day flexibility, but still affords one a way to reasonably make plans around "interdisciplinary" activities (e.g. once this is done, we need to buy those four servers, make sure our legal stuff is taken care of, and pull the trigger on that marketing push one week later, etc). </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload