Dependency (project management)

Last updated

In a project network, a dependency is a link among a project's terminal elements.[ citation needed ]

Contents

The A Guide to the Project Management Body of Knowledge (PMBOK Guide) does not define the term dependency, but refers for this term to a logical relationship, which in turn is defined as dependency between two activities, or between an activity and a milestone. [1]

Standard types of dependencies

There are four standard types of dependencies: [2]

  1. Finish to start (FS)
    • A FS B means "activity A must finish before activity B can begin" (or "B can't start until A has finished"). [3]
      Dependency-FS.png
    • (Foundations dug) FS (Concrete poured)
Finish to finish (FF)
    • A FF B means "activity A must finish before activity B can finish" (or "B can't finish before A is finished") . [3]
      Dependency-FF.png
    • (Last chapter written) FF (Entire book written)
  2. Start to start (SS).
    • A SS B means "activity A must start before activity B can start" (or "B can't start until A has started"). [3]
      Dependency-SS.png
    • (Project work started) SS (Project management activities started)
  3. Start to finish (SF)
    • A SF B means "activity A must start before activity B finishes" (or "B can't finish until A has started")
      Dependency-SF.png
    • (New shift started) SF (Previous shift finished)

Finish-to-start is considered a "natural dependency". The Practice Standard for Scheduling recommends, that "Typically, each predecessor activity would finish prior to the start of its successor activity (or activities)(known as finish-to-start (FS) relationship). Sometimes it is necessarily to overlap activities; an option may be selected to use start-to-start (SS), finish-to-finish (FF) or start-to-finish (SF) relationships....Whenever possible, the FS logical relationship should be used. If other types of relationships are used, they shall be used sparingly and with full understanding of how the relationships have been implemented in the scheduling software being used. Ideally, the sequence of all activities will be defined in such a way that the start of every activity has a logical relationship from a predecessor and the finish of every activity has a logical relationship to a successor". [3]

SF is rarely used, and should generally be avoided. Microsoft recommends to use SF dependency for just-in-time scheduling. [4] It can be easily shown however, that this would only work if resource levelling is not used, because resource levelling can delay a successor activity (an activity, which shall be finished just-in-time) in such a way, that it will finish later than the start of its logical predecessor activity, thus not fulfilling the just-in-time requirement.

There are three kinds of dependencies with respect to the reason for the existence of dependency:

  1. Causal (logical)
    • It is impossible to edit a text before it is written
    • It is illogical to pour concrete before you dig the foundations of a building
  2. Resource constraints
    • It is logically possible to paint four walls in a room simultaneously but there is only one painter
  3. Discretionary (preferential)
    • I want to paint the living room before painting the dining room, although I could do it the other way round, too

Early critical path-derived schedules often reflected only on causal (logical) or discretionary (preferential) dependencies because the assumption was that resources would be available or could be made available. Since at least the mid-1980s, competent project managers and schedulers have recognized that schedules must be based on resource availability. The critical chain method necessitates taking into account resource constraint-derived dependencies as well.

Leads and lags

Dependencies can be modified by leads, and lags. Both leads and lags can be applied to all 4 types of dependencies.

PMBOK defines lag as "the amount of time whereby a successor activity will be delayed with respect to a predecessor activity".

For example: When building two walls from a novel design, one might start the second wall 2 days after the first so that the second team can learn from the first. This is an example of a lag in a Start-Start relationship.

In accordance to PMBOK a lead is "the amount of time whereby a successor activity can be advanced with respect to a predecessor activity For example, on a project to construct a new office building, the landscaping could be scheduled to start prior to the scheduled punch list completion. This would be shown as a finish-to-start with two-week lead". [1]

Example

If you are building a building, you can't paint the walls before installing the water pipes into the walls.

Advanced cases of activities dependencies

Maximal-type relationships

Activity A and Activity B are said to have a Maximal-Type Relationship, if Activity B can start after Activity A, but with the delay of no more than X. [5] Real life examples, which are simulated by Maximal-Type Relation:

Maximal-type relationships are rarely implemented in the project management software, most probably because with this feature it is too easy to create contradictory dependencies.

See also

Citations

  1. 1 2 A Guide to the Project Management Body of Knowledge: PMBOK Guide. Project Management Institute, Incorporated. 1 January 2013. ISBN   978-1-935589-67-9.
  2. ↑ Mulcahy 2021, p. 173.
  3. 1 2 3 4 Practice Standard for Scheduling. Project Management Institute. 2011. ISBN   978-1-935589-24-2.
  4. ↑ "Microsoft article of SF links for Microsoft Project". Archived from the original on 2014-02-02.
  5. ↑ "ProJack Manager web site, describing maximal-type relationships". Archived from the original on 2014-02-03.

Related Research Articles

Project planning is part of project management, which relates to the use of schedules such as Gantt charts to plan and subsequently report progress within the project environment. Project planning can be done manually or by the use of project management software.

<span class="mw-page-title-main">Project Management Body of Knowledge</span> Body of knowledge for project management

The Project Management Body of Knowledge (PMBOK) is a set of standard terminology and guidelines for project management. The body of knowledge evolves over time and is presented in A Guide to the Project Management Body of Knowledge, a book whose seventh edition was released in 2021. This document results from work overseen by the Project Management Institute (PMI), which offers the CAPM and PMP certifications.

<span class="mw-page-title-main">Critical path method</span> Method of scheduling activities

The critical path method (CPM), or critical path analysis (CPA), is an algorithm for scheduling a set of project activities. A critical path is determined by identifying the longest stretch of dependent activities and measuring the time required to complete them from start to finish. It is commonly used in conjunction with the program evaluation and review technique (PERT).

Project management software (PMS) can help plan, organize, and manage resource tools and develop resource estimates. Depending on the sophistication of the software, it can manage estimation and planning, scheduling, cost control and budget management, resource allocation, collaboration software, communication, decision-making, quality management, time management and documentation or administration systems. Numerous PC and browser-based project management software and contract management software products and services are available.

<span class="mw-page-title-main">Program evaluation and review technique</span> Statistical tool used in project management

The program evaluation and review technique (PERT) is a statistical tool used in project management, which was designed to analyze and represent the tasks involved in completing a given project.

<span class="mw-page-title-main">Gantt chart</span> Type of chart to show a project schedule

A Gantt chart is a bar chart that illustrates a project schedule. It was designed and popularized by Henry Gantt around the years 1910–1915. Modern Gantt charts also show the dependency relationships between activities and the current schedule status.

<span class="mw-page-title-main">Project network</span> Diagram showing the order of activities

A project network diagram is a graph that displays the order in which a project’s activities are to be completed. Derived from the work breakdown structure, the terminal elements of a project are organized sequentially based on the relationship among them. It is typically drawn from left to right to reflect project chronology.

A lead time is the latency between the initiation and completion of a process. For example, the lead time between the placement of an order and delivery of new cars by a given manufacturer might be between 2 weeks and 6 months, depending on various particularities. One business dictionary defines "manufacturing lead time" as the total time required to manufacture an item, including order preparation time, queue time, setup time, run time, move time, inspection time, and put-away time. For make-to-order products, it is the time between release of an order and the production and shipment that fulfill that order. For make-to-stock products, it is the time taken from the release of an order to production and receipt into finished goods inventory.

<span class="mw-page-title-main">Precedence diagram method</span>

The precedence diagram method (PDM) is a tool for scheduling activities in a project plan. It is a method of constructing a project schedule network diagram that uses boxes, referred to as nodes, to represent activities and connects them with arrows that show the dependencies. It is also called the activity-on-node (AON) method.

<span class="mw-page-title-main">Schedule</span> Planning of tasks and events

A schedule or a timetable, as a basic time-management tool, consists of a list of times at which possible tasks, events, or actions are intended to take place, or of a sequence of events in the chronological order in which such things are intended to take place. The process of creating a schedule — deciding how to order these tasks and how to commit resources between the variety of possible tasks — is called scheduling, and a person responsible for making a particular schedule may be called a scheduler. Making and following schedules is an ancient human activity.

In project management, resource leveling is defined by A Guide to the Project Management Body of Knowledge as "A technique in which start and finish dates are adjusted based on resource limitation with the goal of balancing demand for resources with the available supply." Resource leveling problem could be formulated as an optimization problem. The problem could be solved by different optimization algorithms such as exact algorithms or meta-heuristic methods.

A hammock activity is a schedule or project planning term for a grouping of tasks that "hang" between two end dates it is tied to.

In project management, level of effort (LOE) is a support-type project activity that must be done to support other work activities or the entire project effort. It usually consists of short amounts of work that must be repeated periodically. Examples of such an activity may be project budget accounting, customer liaison, or oiling machinery during manufacturing.

A glossary of terms relating to project management and consulting.

<span class="mw-page-title-main">Project management triangle</span> Model of the constraints of project management

The project management triangle is a model of the constraints of project management. While its origins are unclear, it has been used since at least the 1950s. It contends that:

  1. The quality of work is constrained by the project's budget, deadlines and scope (features).
  2. The project manager can trade between constraints.
  3. Changes in one constraint necessitate changes in others to compensate or quality will suffer.

Arrow diagramming method (ADM) is a network diagramming technique in which activities are represented by arrows. ADM is also known as the activity-on-arrow (AOA) method.

The Graphical Path Method (GPM) is a mathematically based algorithm used in project management for planning, scheduling and resource control. GPM represents logical relationships of dated objects – such as activities, milestones, and benchmarks – in a time-scaled network diagram.

PLANTA Project is a Project management software for the planning and control of projects that share the same resources. PLANTA Project is the successor to the multi-project management system PPMS, which was introduced in 1980. Unlike its predecessor PPMS, PLANTA Project offers process-oriented project management and has a revised workflow-oriented interface, based on the open-source programming language Python, and MS .NET with panel technology which enables users to position windows as required.

The following outline is provided as an overview of and topical guide to project management:

<span class="mw-page-title-main">Critical path drag</span> Project management metric

Critical path drag is a project management metric developed by Stephen Devaux as part of the Total Project Control (TPC) approach to schedule analysis and compression in the critical path method of scheduling. Critical path drag is the amount of time that an activity or constraint on the critical path is adding to the project duration. Alternatively, it is the maximum amount of time that one can shorten the activity before it is no longer on the critical path or before its duration becomes zero.

References

This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.