Nightingale Case data entry

Nightingale Case data entry

Setting Lag for Predecessors: “FS – 8 time units” means “finish-start” relationship between predecessor and task. Extra Instruction 1: To add lag, add task and predecessor, then double click on task, a menu box opens, go to predecessor tab, there you will see predecessor….add lag in the lag column. FS is the default. Lag = 8 (Not minus 8).
Remember: lag is a delay so you have to add it “+” not “-“
Any comments / answers to questions should be included in the MS Project files using the “note” function.
Extra Instruction 2: For the note function: double-click on a task and select the note tab in the pop up menu. You can general questions in a “note” attached to the last task….specific comment about any specific task should be in a “note” on that task.
Make sure you do the three instructions marked here in RED in addition to the other steps from the Checklist. Extra Instruction 3: Add “Total Slack” column to the Gantt/Entry view using the drop down menu in the “Add new Column” column.

For Nightingale B

Expediting a project is also called “crashing” the project (or expediting the project. Remember to do this, that we need to crash/expedite the lowest cost activity that is available to be expedited and which is also on the critical path).
For example:
If you have two sequential activities A –> B, where A=5 days and B=3 days duration. Then the total project duration is 8 days.
If you need this project completed in 6 days, you have two options:
Option 1: Add resources to reduce duration of activities A by 2 days OR B by two days OR both A and B by 1 day each.
Option 2: If you are able to, do both activities in parallel (without additional resources). So you could start both on the same day, and the project will get done in 5 days. Here A and B are running in parallel in first three days, and then B is completed,
and A is completed two days later. Here the predecessor for B is A with SS (start-to-start) with no lag.
You could also start A, and then start B three days later. Here we have the predecessor for B is A with SS and lag of 3 days.
You could also finish A and B on the same day (day 5) where the predecessor for B is A with FF (finish-to-finish). Project duration is 5 days here.

The first part of Nightingale B is like Option 1 where additional resources are used to reduce activity duration.
The second part of Nightingale B is like Option 2 where the predecessor relationships are being changed to reduce project duration.
In the first part of Nightingale B, you will need to select which tasks to crash. Here the “rule of thumb” is: crash the “cheapest available activity on the critical path” first. Then repeat this rule till you have (a) achieved your target duration, or (b) have no more resource (budget), or (c) have no more activities that can be crashed. Reason: To reduce project duration, the critical path has to be reduced. The other requirement is that the nature of work of that critical path activity should be such that it can be expedited (available). When there are many such activities available to crash on the critical path, we choose the least cost (cheapest), to maximize the impact of our resource/investment.
In the second part of Nightingale B, you will have to try one option at a time and see impact on project duration. If there is no impact, you will reverse the change in predecessors to the original.