none
Auto Schedule/ Adjust start dates for the remaining tasks on task completion - Project Server 2013 RRS feed

  • Question

  • Hi Guys,

    I have a requirement like below.

    Initially i will configure tasks with estimated work hours and  assign them to respective resources and during the execution of those tasks if the resource took less time to finish it then other tasks start date should automatically updated.

    Example:

    1 Task1 20-Feb-2013 21-Feb-2013     16h

    2 Task2 22-Feb-2013 22-Feb-2013  1 Predessor   8h

    If the task 1 completed on 20-Feb its self with in 4 hours then the task 2 is the next one to execute so it should move the start date to 20-Feb-2013.

    How can i achieve this, seems such functionality available in other scheduling tools.

    Appreciate your help!

    -

    P

    Wednesday, February 20, 2013 7:04 PM

Answers

  • Praveen --
     
    If you use either of the methods I mentioned, yes, the Start date of the successor task will be scheduled to start earlier.  A project manager can bypass the task update approval process by creating a Rule to automatically approve task updates.  You create Rules from the Approval Center page in PWA.  I must warn you before you start using Rules to auto-approve task updates.  If a team member makes a mistake entering progress in PWA, and submits the progress to you as the PM, and you use a Rule to automatically approve task updates, the mistake gets pushed into your project.  And there is no Undo feature that you can use to remove the mistake from the project.  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"

    Thursday, February 21, 2013 1:52 PM
    Moderator

All replies

  • Praveen --
     
    What method of tracking are you using in your Project Server 2013 system?  It would help if we know that.
     
    For Task 1, your team member would need to enter 12 hours of Actual Work and change the Remaining Work to 0 hours.  If the team member merely enters a Percent Work Complete value of 100%, Project Server 2013 has no way of knowing that the task completed early.  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"

    Wednesday, February 20, 2013 9:11 PM
    Moderator
  • Hi Dale,

    Thank you so much for your reply.

    We are open to any of the method which is supported by project server:

    1. Percent of Work Complete
    2. Actual work done and work remaining
    3. Hours of work done per period

    I hope there will be a way to specify that the task completed early and actual hours took to complete that task, at the same time reporting hours should not change actual estimates (we can use Base line but i want to know any way to achieve with out Base line). Also, next tasks should adjust their start time based on previous tasks so the resource time will be utilized appropriately.

    This is very common situation across project scheduling, some times we estimate more and finish them quickly and accommodate the pending efforts to another task. The same i want to get it done using MS project scheduling automatically based on updated task details.

    Hope i provided more info.

    Thursday, February 21, 2013 7:02 AM
  • Praveen --
     
    To meet your tracking requirements, your organization could use either the Actual Work Done and Work Remaining method of tracking, or the Hours of Work Done Per Period method in Project Server 2010.  The key to using either method is to allow team members to set the Remaining Work to 0h on any task they finish in less time than originally estimated.  From your original example, the team member worked 12 hours on a 16-hour task, and finished early.  Using this example, the team member would enter 12 hours of Actual Work and change the Remaining Work to 0 hours.
     
    No matter which method of tracking you use, you MUST use a baseline to capture your original estimates in the project.  So, no, there is no way to keep your original estimates without using a baseline.
     
    And yes, I agree that your situation is pretty common.  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"

    Thursday, February 21, 2013 9:22 AM
    Moderator
  • Dale,

    Thanks Again.

    So this will automatically change the next task start date ahead as the previous task complete before the scheduled time?

    Also, i have followup question.

    Is there any option to remove approvals for submitted tasks?

    If no, how we can submit tasks update with out sending them for approval or review?

    Thanks

    P

    Thursday, February 21, 2013 1:06 PM
  • Praveen --
     
    If you use either of the methods I mentioned, yes, the Start date of the successor task will be scheduled to start earlier.  A project manager can bypass the task update approval process by creating a Rule to automatically approve task updates.  You create Rules from the Approval Center page in PWA.  I must warn you before you start using Rules to auto-approve task updates.  If a team member makes a mistake entering progress in PWA, and submits the progress to you as the PM, and you use a Rule to automatically approve task updates, the mistake gets pushed into your project.  And there is no Undo feature that you can use to remove the mistake from the project.  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"

    Thursday, February 21, 2013 1:52 PM
    Moderator