Change a task link - Project
In Microsoft Office Project, you can create dependencies between tasks in the same project, and between tasks in different projects. Project offers four kinds of task dependencies: finish-to-start, In a finish-to-start dependency, the second task in the relationship can't begin until the first task finishes. For example, in the Relationship Diagram view shown in Figure 1, notice Notice also that you can see that the dependency relationship is Finish-to-Start ( FS) with He is the co-author of 20 books on Microsoft Project and Project Server. Delivering Agile Projects using Microsoft Project/Project Online. Project Essentials" class, focused purely on Microsoft Project This relationship should be used when a task can only be started.
The most common example is concrete, in which a lag is inserted between tasks to allow the concrete time to cure before the successor task can proceed. A lead has the opposite effect on the schedule. A lead is the amount of time that a task can start before the completion of the first task.
Many schedulers refer to lead as a negative lag. Note that the use of leads is discouraged by scheduling guidelines. These summary tasks are elements of the work breakdown structure, and will not have assigned relationships. This relationship assignment has no lag, so leave the lag as 0d.
Back to Basics: Understanding task dependencies
Next select the Task tab, Schedule ribbon group, and link icon, Figure 7. Your Finish-to-Start relationship for these two tasks is applied as displayed in Figure 8. Figure 9 Again, your tasks with the Finish-to-Start relationship will be as shown in Figure Figure 11 The result is in Figure This is the input for the standard business time lag.
However, our lag is not standard. In the Lag column of the Task Information dialog for Predecessors, Figure 13, type in 5ed, which stands for five elapsed days. Figure 13 Click OK, and your elapsed time lag will be as displayed in Figure Figure 14 Assigning a Finish-to-Finish Relationship Now we are going to assign two tasks a Finish-to-Start relationship, and edit it to make the relationship Finish-to-Finish.
Types of task links - Project
So, for example, if you were planning a project to make a wedding cake, you might use a finish-to-start dependency between the "Bake cake" and "Decorate cake" tasks. When the "Bake cake" task is finished, the "Decorate cake" task begins. Start-to-start SS dependencies are used when the second task in the relationship can't begin until after the first task in the relationship begins. Start-to-start dependencies don't require that both tasks start at the same time. They simply require that the first task has begun, in order for the second task to begin.
Going back to the wedding cake example, let's say you had planned to make the icing for the cake while the cake is baking in the oven.
You can't start making the icing until the cake has started baking, so you might use a start-to-start dependency between the "Bake cake" and "Make icing" tasks. If one of your tasks can't finish until another one finishes, you can use a finish-to-finish FF dependency between them. Finish-to-finish dependencies don't require that both tasks be completed simultaneously. They simply require that the first task be finished, in order for the second task to finish.Microsoft Project 2010: Modifying Task Relationship Types
The second task can finish any time after the first task finishes. Notice that the Relationship Diagram pane shows the names and ID numbers of all of the direct Predecessors and director Successors for the selected task, along with the task dependency types for each task. Task Sheet with Relationship Diagram view Figure 5 shows a combination view with the Task Usage view in the top pane and the Relationship Diagram view in the bottom pane.
Because the Task Usage view contains a timephased grid rather than a Gantt Chart, you cannot see task dependency relationships. However, when you include the Task Usage view in a combination view with the Relationship Diagram view, you can easily determine task dependency relationships. For example, notice in Figure 5 that the selected task in the Task Usage pane has two direct Predecessors and four director Successors, as shown in the Relationship Diagram pane.
Task Usage with Relationship Diagram view Figure 6 shows a combination view with the Resource Usage view in the top pane and the Relationship Diagram view in the bottom pane. Because the Resource Usage view is a resource view that also shows task assignments, you cannot see task dependency relationships for the task assignments.
However, when you include the Resource Usage view in a combination view with the Relationship Diagram view, you can select any task assignment and then easily determine task dependency relationships. For example, notice in Figure 6 that the selected task assignment in the Resource Usage pane has one direct Predecessor and three director Successors, as shown in the Relationship Diagram pane.