none
Team Planner - Contraint Dates RRS feed

  • Question

  • With Project Professional 2010 there are now 2 ways to level resource.  The "Level Resource/ Level All" tool and the "Team Panner".  Both of which will work well, in earlier version you only had the "Level Resource" tool.

    My questions is.

    Why with the "Team Planner" do they use contraint dates instead of "Leveling Delay" as is done with the leveling tool? 

    Is is possible to have the team planner use leveling delay instead?   I hate putting contraint dates on tasks simply to level resource. 

    Why would Microsoft implement basicly the same functionality in two different methods (because 2 different developers I would suspect.)

    Thanks,

     

    Fletcher

    Tuesday, May 3, 2011 6:47 PM

Answers

  • FHearns1 --

    Actually there are now multiple ways to level an overallocated resource:

    1.  You can level the overallocated resource in the Resource Usage view using the Level Resource button on the Resource ribbon.

    2.  You can level the overallocated resource in the Team Planner view using the Level Resource button.

    3.  You can level the overallocated resource in the Team Planner view by dragging a task from an overallocated resource to an available resource.

    4.  You can level an overallocated resource on a task by task basis in the Gantt Chart view by right-clicking on a task to which the overallocated resource is assigned, and then selecting the Schedule to Available Date item in the shortcut menu.

    If you choose options #1, #2, or #4, Microsoft Project 2010 places a Leveling Delay on one or more tasks to resolve the overallocation.  If you select option #3 only, Microsoft Project 2010 places a Start No Earlier Than (SNET) constraint on the task that you drag from one resource to another. So, if you do not want the software to place the SNET constraint on tasks, DO NOT drag a task from one resource to another in the Team Planner view. Instead, use one of the other three options.  Hope this helps.


    Dale A. Howard [MVP]
    VP of Educational Services
    msProjectExperts
    http://www.msprojectexperts.com
    http://www.projectserverexperts.com
    "We write the books on Project Server"

    Tuesday, May 3, 2011 7:46 PM
    Moderator
  • Dale,

    Thanks for the reply.  

    I have actually chosen a slightly different aproach that is working for my needs.

    I actualy use the "Task Inspector" in the "Team Planner" view.  To do this I select the "Task Inspector" from the "Task" ribbon while in the "Team Planner" view.  

    This allows me to select and individual task for an over allocated resource and then using the "Repair Option" to reschedule the task to next available time within the "Task Inspector".   This has the benifit of letting me control which task is rescheduled while still using a leveling delay instead of a SNET contraint. It also allows me to play what if games with the rescheduling to task to see which has the least effect on the Project end date as well as other resource overallocations.

    Again thanks for the help.

     

    Regards,

     

     

    Fletcher

    Sunday, May 8, 2011 12:48 PM

All replies

  • FHearns1 --

    Actually there are now multiple ways to level an overallocated resource:

    1.  You can level the overallocated resource in the Resource Usage view using the Level Resource button on the Resource ribbon.

    2.  You can level the overallocated resource in the Team Planner view using the Level Resource button.

    3.  You can level the overallocated resource in the Team Planner view by dragging a task from an overallocated resource to an available resource.

    4.  You can level an overallocated resource on a task by task basis in the Gantt Chart view by right-clicking on a task to which the overallocated resource is assigned, and then selecting the Schedule to Available Date item in the shortcut menu.

    If you choose options #1, #2, or #4, Microsoft Project 2010 places a Leveling Delay on one or more tasks to resolve the overallocation.  If you select option #3 only, Microsoft Project 2010 places a Start No Earlier Than (SNET) constraint on the task that you drag from one resource to another. So, if you do not want the software to place the SNET constraint on tasks, DO NOT drag a task from one resource to another in the Team Planner view. Instead, use one of the other three options.  Hope this helps.


    Dale A. Howard [MVP]
    VP of Educational Services
    msProjectExperts
    http://www.msprojectexperts.com
    http://www.projectserverexperts.com
    "We write the books on Project Server"

    Tuesday, May 3, 2011 7:46 PM
    Moderator
  • Dale,

    Thanks for the reply.  

    I have actually chosen a slightly different aproach that is working for my needs.

    I actualy use the "Task Inspector" in the "Team Planner" view.  To do this I select the "Task Inspector" from the "Task" ribbon while in the "Team Planner" view.  

    This allows me to select and individual task for an over allocated resource and then using the "Repair Option" to reschedule the task to next available time within the "Task Inspector".   This has the benifit of letting me control which task is rescheduled while still using a leveling delay instead of a SNET contraint. It also allows me to play what if games with the rescheduling to task to see which has the least effect on the Project end date as well as other resource overallocations.

    Again thanks for the help.

     

    Regards,

     

     

    Fletcher

    Sunday, May 8, 2011 12:48 PM
  • Fletcher --

    Well, you have now pointed out even ONE MORE way to level resource overallocations!  Thanks for sharing.  :)


    Dale A. Howard [MVP]
    VP of Educational Services
    msProjectExperts
    http://www.msprojectexperts.com
    http://www.projectserverexperts.com
    "We write the books on Project Server"

    Sunday, May 8, 2011 4:41 PM
    Moderator