Baseline
A schedule baseline is a frozen snapshot of an approved state, used as the reference against which execution variances are measured. Without an archived baseline, reliable progress reporting is not possible.
See also : Milestone
Definitions of the foundational terms of project scheduling and steering, as we use them in linXera. Every term is anchored and shareable.
A schedule baseline is a frozen snapshot of an approved state, used as the reference against which execution variances are measured. Without an archived baseline, reliable progress reporting is not possible.
See also : Milestone
The critical path is the sequence of dependency-linked tasks that determines the total duration of a project. Any critical-path task that slips pushes the project end date by the same amount because its total float is zero.
See also : Total float, Milestone
A Finish-to-Start (FS) dependency requires that the successor task cannot start until its predecessor task finishes. It is the most common dependency type and the default in most scheduling tools.
See also : Critical path
The free float of a task is the maximum delay it can absorb without delaying the early start of its immediate successor. It is always less than or equal to the total float.
See also : Total float
A milestone is a zero-duration event that marks a checkpoint on a schedule : a delivery, a decision, or a formal review. It carries no resource and no effort, and serves as a synchronization marker between stakeholders.
See also : Critical path
The total float of a task is the maximum delay it can absorb without pushing the project end date. A total float of zero means the task lies on the critical path.
See also : Critical path, Free float