none
Project Tracking RRS feed

  • Question

  • Hi,

    I am using Project Tracking via Status Date.

    Used Case Scenario is as below:-

    Bi-Weekly the Project Manager updates the status date to yesterday's date and updates the project via selecting the option for re-scheduling uncompleted work to start after "yesterday's date" for the Entire Project.

    As a result it does pushes the incomplete tasks forward to get a visibility of forecasted finish / completion date but at the same time it also  builds constraints on them wherein the activities does not move forward in the next instance, next week.

    Kindly advise if this is the correct way as to how the project is getting tracked & pushed forward for the uncompleted tasks or tasks wherein no progress is reported and ways to address the issue getting observed.

    Thanks

    Tuesday, May 21, 2019 2:29 AM

All replies

  • Hi,

    Rescheduling the remaining work after the status date should not create new constraints. Is it what you are saying?

    Of course, if your schedule already contains contraints, you might have conflicts between the rescheduling and those constraints. So the best practice is to avoid as much as possible to set constraints on tasks.


    Hope this helps,


    Guillaume Rouyre, MBA, MVP, P-Seller

    Tuesday, May 21, 2019 9:01 AM
    Moderator
  • Hi,

    I have removed all the constraints via "Constraint Type" column changed all to As Soon As Possible, still while re-scheduling uncompleted work to start after: "date" for entire project constraints are getting set.

    Is there anything else am I missing to correct to fix this up.

    Thanks

    

    Tuesday, May 21, 2019 9:53 AM
  • Strange, I just tested it, MS Project does not create any constraints when I reschedule uncomplete work after the status date. Do you have any specificities on this project?

    Hope this helps,


    Guillaume Rouyre, MBA, MVP, P-Seller

    Tuesday, May 21, 2019 10:08 AM
    Moderator
  • Hi,

    Interestingly, I observed the activities wherein there is 0% are getting constrained for "start no earlier than" to the status date while activities wherein any no. between 1-99% looks fine on the 1st re-schedule

    Tuesday, May 21, 2019 10:42 AM
  • Indeed you're right. If the task as no actual work, MS Project does need to set a constraint on the start date to position it. This is by design: there is only a few ways to set a task start date: constraint, actual project start date... That being said, it should not be an issue to have a "start no earlier than" constraint on the status date since tasks cannot move backward this status date.

    Hope this helps,


    Guillaume Rouyre, MBA, MVP, P-Seller

    Tuesday, May 21, 2019 12:55 PM
    Moderator
  • Let's say that a task is entirely scheduled in the past relative to the status date.

    The status date is displayed as a vertical red line on the chart (gridlines) and the task bar is entirely to the left of the red line.

    If a task is scheduled in the past relative to the status date and it has not actually started, then it must be re-scheduled to start asap in the future, ie at or immediately after the status date.

    You use the move button to "move incomplete parts to the status date".

    And yes, MSP will give it a SNET constraint to achieve this. Now usually we want to avoid date constraints and have all tasks asap. But this is one of those cases where a date constraint is OK. What you really want to avoid is date constraints on tasks that are scheduled any further in the future than this.

    Tuesday, May 21, 2019 8:23 PM
  • Hi,

    Via tracking or pushing forward the tasks, split tasks gets created whereby the task duration and the (finish date)-(start date) do not match, which may could be misleading at times.

    In the current scenario, I am getting the daily progress updated as below:

    1. Consumed hours in the Task updation and approvals via PWA

    2. Remaining Duration of the Tasks  updation and approvals via PWA

    3. Re-scheduling the incomplete work to start after the status date

    Is that the right way to track.. to push the pending or incomplete tasks after the status date or are there any better ways to track kindly advise.

    Thanks

    Tuesday, May 21, 2019 8:38 PM
  • Consumed hours is actual work. Try this instead. Start with the most basic information first, and deal with the facts in the order in which they occur.

    The task has actually started or it hasn't. If it hasn't, then move the entire task to the status date.

    If it has actually started, when did it actually start? Input the actual start date/time into the actual start field in the tracking table (where else?). Obviously the actual start date/time must be in the past relative to the status date.

    Next, what is the actual duration since the actual start and up to the status date? Obviously, there cannot be any actual duration to the right of the status date. That means the black line on the bar cannot be allowed to extend beyond the status date. If a task actually started 6 days ago then the maximum actual duration is 6 days. But it may be fewer. If the task actually started 6 days ago, and you have input the actual start date/time, then input the actual duration as whatever it was, which may be 6, or it may be say only 2. If it was only 2, then the 4 days of scheduled duration on the left of the status date has to be re-scheduled to the status date. Yes, MSP will split the task, leaving the actuals where they occurred and moving the scheduled part to asap into the future, which is the only place where it can occur.

    Once you have nailed down the actual duration, you can be 100% certain that any actual work and any actual cost must have occurred during those days of actual duration. Use the task usage view to input the actual work that occurred on each of the days of actual duration.

    Then check the remaining duration and adjust as necessary, and check the remaining work which is scheduled to occur on those days of remaining duration.

    Wednesday, May 22, 2019 4:28 AM
  • Hi,

    While updating actual progress for Tasks through MSP is it mandate to update as per the below sequence only, while the reverse can lead to undesirable results:-

    1. % Complete

    2. Actual Start (Change or update if needed)

    Thanks


     
    Wednesday, May 22, 2019 9:46 AM
  • Are there any potential demerits / limitations of tracking the project via status date ie. pushing the incomplete work ahead of the status date daily?

    One of the observation is that the duration which earlier used to be finish - start is not the case now as work days / hours may be the right reflection as the tasks are split tasks now... views pls

    Also, will the tasks get split at multiple times as well in case there is work stopped at multiple intervals.

    Tuesday, May 28, 2019 6:40 PM
  • You have more likelihood of getting answers if you ask better questions. Your questions are vague, ambiguous and just about incoherent. You don't provide any examples of anything you have tried. You don't mention that you have tried anything that has already been suggested.

    I refer to my earlier advice. Further, do not type in % complete. MSP will calculate that for you.

    This is a task that was interrupted several times

    Tuesday, May 28, 2019 11:20 PM
  • Task having constraint and predecessor linkages as well.

    How can it be checked which one will be applicable.

    Thanks

    Wednesday, May 29, 2019 5:26 AM
  • Trevor Rabey, Pl advise

    Also, there pushing teh plan forward via the status date tracking enables SNET constraint on them while there could an instance wherein a current activity completes ahead of schedule and should enable the successor activities to push backwards as well

    Tuesday, June 18, 2019 9:14 AM
  • Hi,

    Any updates / inputs Pl

    Wednesday, June 26, 2019 6:39 AM