A dependency between two project activities, or between a project activity and a milestone. See also precedence relationship. The four possible types of logical relationships are:
A network path that passes the same node twice. Loops cannot be analyzed using traditional network analysis techniques such as critical path method and program evaluation and review technique. Loops are allowed in graphical evaluation and review technique
A summary-level schedule that identifies the major activities and key milestones. See also milestone schedule.
See network analysis.
Any organizational structure in which the project manager shares responsibility with the functional managers for assigning priorities and for directing the work of individuals assigned to the project.
A significant event in the project, usually completion of a major deliverable.
A summary-level schedule that identifies the major milestones. See also master schedule.
See risk mitigation.
The capture, analysis, and reporting of project performance, usually as compared to plan.
A technique that performs a project simulation many times to calculate a distribution of likely results. See simulation.
An activity that has low total float.
See project network diagram.
The process of identifying early and late start and finish dates for the uncompleted portions of project activities. See also critical path method, program evaluation and review technique and graphical evaluation and review technique.
The collection of activity dependencies that makes up a project network diagram.
Any continuous series of connected activities in a project network diagram.
One of the defining points of a network; a junction point joined to some or all of the other dependency lines. See also arrow diagramming method and precedence diagramming method.
A depiction of the project organization arranged so as to relate work packages to organizational units.
Identifying, documenting and assigning project roles, responsibilities, and reporting relationships.