BookRags.com Literature Guides Literature
Guides
Criticism & Essays Criticism &
Essays
Questions & Answers Questions &
Answers
Lesson Plans Lesson
Plans
My Bibliography Periodic Table U.S. Presidents Shakespeare Sonnet Shake-Up
Research Anything:        
History | Encyclopedias | Films | News | Create a Bibliography | More... Login | Register | Help
Not What You Meant?  There are 16 definitions for Dependency.  Also try: Lag.

Dependency (project management)

Print-Friendly
About 1 pages (370 words)

Bookmark and Share Questions on this topic? Just ask!

In a project network, a dependency is a link amongst a project's terminal elements. There are four kinds of dependencies with respect to ordering terminal elements (in order of decreasing frequency of use):

  1. Finish to start (FS)
    • A FS B = B doesn't start before A is finished
    • image:Dependency-FS.png
    • (Foundations dug) FS (Concrete poured)
  2. Finish to finish (FF)
    • A FF B = B doesn't finish before A is finished
    • image:Dependency-FF.png
    • (Last chapter written) FF (Entire book written)
  3. Start to start (SS).
    • A SS B = B doesn't start before A starts
    • image:Dependency-SS.png
    • (Project work started) SS (Project management activities started)
  4. Start to finish (SF)
    • A SF B = B doesn't finish before A starts
    • image:Dependency-SF.png
    • (New shift started) SF (Previous shift finished)

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
  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

Traditional critical path-derived schedules are based only on causal (logical) dependencies. The critical chain method necessitates taking into account resource constraint-derived dependencies as well. Time related information can be used in conjunction with any of the relationships for any of the reasons outlined above. This is known as a lead or lag. For example: When building two walls from a novel material, one might start the second wall 2 days after the first so that the second team can learn from the first. It is also useful to use lead/lag when tasks are in parallel in a Finish-Finish relationship. For example: The document for 'Activity A' should finish 5 days before the document for 'Activity B' so that the reviewers have time to read each individually. Although Document A and Document B may take different times to write, they will be planned to finish 5 days apart.

See also

View More Summaries on Dependency (project management)
 
Ask any question on Dependency (project management) and get it answered FAST!
Answer questions in BookRags Q&A and earn points toward
discounted or even FREE Study Guides and other BookRags products!
Learn more about BookRags Q&A
Copyrights
Dependency (project management) from Wíkipedia. ©2006 by Wíkipedia. Licensed under the GNU Free Documentation License. View a list of authors or edit this article.

Article Navigation
Join BookRagslearn moreJoin BookRags




About BookRags | Customer Service | Report an Error | Terms of Use | Privacy Policy