But you could easily mix and match within a single resource. When I assign a weekend-working-only resource to a task MS-P will only schedule it to be worked on over the weekend. So I create two (or more) different resources, one with weekday working and one with weekend working. Typically I have normal working resources, set up the usual way, and then specific weekend-working resources who work weekend shifts to get stuff done, but do not work normal weekdays. On prior versions of MS-P, if I can remember correctly, you need to select Sat and Sun in the column headers of the calendar box and then click the radio button indicating Working Days or Non-Standard Working Days (in which case you need to manually enter the hours they work on the selected days). You can add as many rows describing non-standard hours as you want. Accept the changes and ensure the dates are correct for the period of time the resource is working the new hours. In 2010 onward you go to the Working Week tab and enter a new entry, then select the 'Details' button and ensure you have selected all days on which the user is working. Having opened the resource's calendar's Change Working Time dialog it now differs depending on verison. A common source of confusion is that the calendar is named the same as the Project's calendar, but when selected from the Resource Sheet is specific and personal to that user alone. In both versions you go to the Resource Sheet, select the resource you want to modify and double-click on their calendar (right hand side of sheet). It changed slightly from MS-P 2010 onwards. How you set the working time for resources differs depending on which version of Project you are using. If the resource(s) assigned are permitted to work on Saturday and Sunday then any tasks to which they are assigned will automatically be scheduled on those days. It is just a matter of setting the correct working time for the resources assigned to the task. I would love it if someone would do a deep-dive webinar on critical path puzzles like this.I have planned many projects where tasks were permitted to be worked on over weekends. Converting both tasks to fixed duration restored the Total Slack values for those 4 tasks to zero. I’m struggling to understand why the intervening 4 tasks gained non-zero Total Slack values. Everything in that chain had an ASAP constraint type. It’s doppleganger has 1 day of slack.įive predecessors upstream in the critical path I extended the duration of a fixed duration, critical, task by a single day and everything between that extended task and the 16 hr task gained a non-zero slack and, thereby, was dropped from the critical path. Though they are nominally 2 weeks in duration the 16hr task appears a tiny bit longer on the gantt chart and has zero days of slack. I have 2 tasks assigned to different resources both nominally of 2 wks duration with task type of Fixed Units- One was 80 hrs and the other 16 hrs. I have some fundamental misconceptions about Task Type which has caused me a lot of grief. I ‘solved’ my problem but I’m really having a hard time wrapping my head around the explanation. Project Portfolio Management (PPM) Training.Project Management Office (PMO) Training.goals, scheduling, task allocation, parallel working on the same task and. Enterprise Project Management (EPM) Training the market, four were selected, ProjectLibre, Redmine, Microsoft Project 2013.Project Management Certification Training.

Projectlibre forward schedule