I have a project completed in MS Project but I made an error on the start date. How do I change the start date to another date so that all other dates automatically change? I tried just changing the start date but the other dates will not change?
Have you specified Predecessor links between the individual Tasks? If so, you can simply change the Start of the first Task and all the others will move. If not add Predecessor links between the tasks - even if they're just to set them all to the same Start (e.g. if you want the Task in Row 4 to start at the same time as the one in Row 3, enter 3SS in Predecessors for Row 4). Then change the Start of the first Task; the rest will move and the Project Start will also be automatically updated.
If your tasks are all "automatically scheduled" then moving one task to a later date should automatically move the others. If your tasks are "manually scheduled" then they won't automatically adjust. Switch all tasks to "automatically scheduled" and it should fix it! ^-^
All the best!
Matthew
Related
Description
While importing the XML in MS Project then the start and finish dates get changed.
Please find the dates in XML
Start and end date in XML
Please find the MS output
MS Project output
Get the XML file from here https://github.com/VigneshRameshh/GanttIssue
Help me to find the reason behind this?
Thanks in advance,
Vignesh Ramesh.
There are several factors that are affecting this.
The calendar that is applied to the project in the XML is the project's "Standard" calendar. This calendar only has 8 hour working days Monday-Friday, starting at 8:00 and ending at 17:00.
The amount of minutes of working time per day is set to 480, which is 8 hours
The task is Auto Scheduled, not manually scheduled (the value would be 1 if it was manually scheduled).
Given those parameters, MS Project cannot have the start of the task begin at 10/22/21 00:00 and finish on 10/23/21 00:00. Because the task is Auto scheduled, it must follow the Project's calendar and hours per day requirements. Therefore MS Project will start the task at the earliest point on 10/22/21 (8:00) and follow the 1 day duration applied to it, which will cause it to end on 10/22/21 17:00.
Note - it is not recommended to have tasks set to be Manually Scheduled. You want your tasks to be set to be Auto Scheduled.
Let's say you have a small project. The team has estimated all the tasks as 300 days of effort.
I have 5 developers in the team, and I want MS Project to tell me when the project will complete considering vacations and working schedule of my team member.
In order to do that:
I'm creating a Task "Development" with fixed work "300d", and task type "Fixed Work".
Then I create 5 resources, and specify a 2 week vacation for one of the developers somewhere in the middle of the schedule.
Then I assign my 5 development resources to this task.
The problem is, the 300d distributed evenly to all 5 development resources. And If one of them have a two weeks vacation in between, due to that particular resource the work will be finished 2 weeks later, where other 4 resources are sitting and doing nothing for 2 weeks. Total duration is 70 days.
what I get
What I want to get is: work is distributed accordingly through all 5 resources unevenly in a way that the whole task finishes as earlier as possible taking most of the usable time from all developers.
That's how I would expect it to work. In that particular case I was distributing hours manually.
what i would expect
Is there a possibility in MS Project to do something like this? Or am I doing something wrong?
There are a couple issues with how you are approaching the problem.
1. Rather than just planning out the manpower hours estimated to be needed for the entire project on a single line item, You should plan out the tasks that will need to be done to accomplish "Small Project"
If you discretely plan out the tasks that need to be accomplished to satisfy the scope of "Small project", you can establish dependency (predecessor/successor) relationships between your tasks and figure out what tasks need to be done before you can move on to others. When you do this it will give you a good idea of how long the total duration of the project will take and likely be more accurate than just relying on an estimate based on the manpower hours estimate your developers give you. Find out what tasks they actually need to do, not just how many hours they think the whole project will take them. This will also allow you to plan out the utilization of your resources better because you'll be able to assign specific resources to specific tasks, and not all of your resources need to be on every task.
2. In general I would avoid using the Task Usage form.
I noticed you are altering resources in the task usage form, but unless you are really experienced with Microsoft Project I would avoid ever touching that, as it's really easy to set the period of performance of resources assigned to a task to be different than the actual period of performance of the task itself. This will cause MS Project to behave unusually, and it can be hard for an unexperienced user to understand why. This usually leads to pain and frustration. This leads me to my next bit of advice:
3. If you really want to specify a resource's vacation time, it's better to adjust the calendar associated the resource to exclude those dates as working dates.
In your situation with only 5 resources on your project, this can be fairly easy to do. You can accomplish this 2 different ways (I'll start with the easiest option):
1. You can add resource specific exclusion dates to the default calendar in your project
You can accomplish this by opening the Resource Sheet table and then clicking the Project tab then Change Working Times. If you have the Resource Sheet open instead of the Gantt chart, you can specify the resource that is going to be effected by the exceptions:
In this example you can see that I would be excluding (removing) 8/23/21 thru 9/3/21 as working days for the SW Engineer resource, without needing to change the calendar used by the resource completely.
2. You can completely change the calendar used by particular resources to be different than the default calendar set for the project.
You can accomplish this by going into the Resource Sheet and opening the Base Calendar column:
From here you can assign any calendar that exists in the project to the resource. Of course this means you would need to create the calendars and assign exclusion dates to them.
To create a calendar, click the Project tab then click Change Working Times. Click Create New Calendar on the form that opens up and give it a name:
From there you can add exclusion dates and all that.
Note: In a larger project with many resources, I would recommend not messing with the calendar for the resources at all. It just gets hard to deal with when there are a lot of resources.
I've add my complication entries and this all seems to work well - each complication entry is scheduled for midnight.
I'm testing the time change by setting my Mac's date to the following day where I'm expecting my complication to update to the next entry.
However, it only updates the entry when I open and close my app. I'm expecting to see it automatically change like the other standard complications do. Is this some behaviour I need to go out of my way to implement? I'd expect an automatic change as per the docs.
I've found the following:
ClockKit begins displaying a timeline entry precisely at the time specified by the entry’s date property.
But surely this is a greater than check too? I tried setting it exactly to midnight but (surprisingly) this doesn't work either.
Any help is appreciated.
Additionally, I found the following regarding updating the timeline, but I would have thought this would be for changing the timeline entries as oppose to just refreshing the complication for the current timeline:
During a background app refresh task. You can schedule background tasks to periodically update your watchOS content. This works best when your data changes at predictable times.
The Watch Simulator appears to have some quirks around handling of times. In particular, it doesn’t seem to obey time changes on the underlying system until you relaunch it.
Relaunch the Simulator after changing the system clock and check on your Complication then. If you want to test the transition to the next day specifically, you can set the system time to 11:58 pm and wait for it to cut over.
I am using MS project 2016. My project plan has 700 line items all of them are scheduled auto schedule.
My issue is that Manual Schedule or Auto Schedule Button is greyed out. I have multiple dependencies. I have dependencies, but those dependencies don't seem to work.
For example, When changing the duration, it does update the finish date, but it does not update the start date of the successors, even though I have a Finish to start dependency mapped. How can "reactivate" my mapped dependencies?
Example row 16, if I change the duration to 10 days it does not automatically update row 17. Do you know why?
I have made sure that I do not have any constraints and that all activities are auto scheduled, but that does not work.
I am not sure if this is an issue: but MS project opens ins compatibility mode. Also when I delete the 500 lines of the 700 lines, dependencies of the remaining 200 lines work...
Attached a picture of a couple of line items of the project plan where I have deleted the content of "names" for confidentiality reasons.
CLICK HERE
Thanks
I have a Control-M job that runs every 20 min. Everything works great during that day's run. The issue is when we auto-order the next days jobs. If the current day's jobs are running we get 2 copies of the jobs running at the same time.
Is there a way to not start the new job if the previous day's job is executing?
The job starts every 20 minutes, but how long does it run? Set the end window for "submit between" time a few minutes before the new day build.
Let's say your new day builds at 0400. Since the job is intended to run every 20 minutes, you can have it run as late as 0340. Set the "to" time in Activity Window to 0340 and the job won't autosubmit after that time. The new day will build at 0400 and the new version of the job will start then - 20 minutes after the previous start.
You can also add a control resource to the job to prevent two of them from running at the same time. I don't know another way to do it. That's not a can of worms I'd open unless the activity period settings just won't work the way you want them to.
If you're referring to last day's job execution bleeding into current day, causing resource contention, your best bet (as Rob pointed out) is to define a resource with max count of 1 to be required by the job, so next day job instance cannot start until prev day job completes and release the resource. Alternatively you can have the job post a Condition for order date + 1, and have order date condition also be an In condition for the job.