Terms Flashcards Preview

PMBOK 6th Ed. > Terms > Flashcards

Flashcards in Terms Deck (3)
Loading flashcards...



Lead is the amount of time a successor task can be accelerated. Lead can applied only on finish-to-start relationship between two activities. We can see the below example. In the below example, task B can start 2 days before the completion of task A. Hence the start of task B, which ideally would have been on 6th day, will not start on 4th day.




Lag is the amount of wait time between two tasks. Or in other words, lag is the amount of time by which a successor activity will be delayed. Lag can be used in all the four logical relationships in scheduling, such as Finish-to-start (FS), start-to-start (SS), finish-to-finish (FS) and start-to-finish (SF).

In below example, Task A and B have a Finish to Start (FS) relationship. Ideally both A and B should get finished on the 12th day. But when we insert a waiting of time of 2 days before B can start, then both A and B will get completed only on the 14th day.




Float (also known as slack) is the amount of time by which the start of an activity can be delayed without delaying the project completion time. Every task will have following set of start and finish time.

Earliest start time (ES) - The earliest time, an activity can start once the previous dependent activities are over.
Earliest finish time (EF) - This would be ES + activity duration.
Latest finish time (LF) - The latest time an activity can finish without delaying the project.
Latest start time (LS) - This would be LF - activity duration.
Float time of an activity can be calculated by taking the difference between Late Start (LS) and Early Start (ES) OR between Late Finish (LF) and Early Finish (EF).

Float = LS-ES OR


A positive float time indicates the flexibility we will have in delaying the specific activity without delaying the project completion time.

Typically, while doing scheduling, the critical path tasks will have zero float and the non-critical path tasks will have a positive float. That means non-critical path tasks can be delayed to certain extent without compromising on the project completion time. Float time information of tasks is very useful to the project team for taking scheduling decisions when there will be resource constraints.