Page 185 -

6 - PROJECT TIME MANAGEMENT

A lag is the amount of time whereby a successor activity will be delayed with respect to a predecessor activity.
For example, a technical writing team may begin editing the draft of a large document 15 days after they begin
writing it. This can be shown as a start-to-start relationship with a 15-day lag as shown in Figure 6-10. Lag can
also be represented in project schedule network diagrams as shown in Figure 6-11 in the relationship between
activities H and I, as indicated by the nomenclature SS+10 (start-to-start plus 10 days lag) even though offset is
not shown relative to a timescale.

The project management team determines the dependencies that may require a lead or a lag to accurately
define the logical relationship. The use of leads and lags should not replace schedule logic. Activities and their
related assumptions should be documented. 6

6.3.3 Sequence Activities: outputs

6.3.3.1 Project Schedule network diagrams

A project schedule network diagram is a graphical representation of the logical relationships, also referred to as
dependencies, among the project schedule activities. Figure 6-11 illustrates a project schedule network diagram. A
project schedule network diagram is produced manually or by using project management software. It can include
full project details, or have one or more summary activities. A summary narrative can accompany the diagram and
describe the basic approach used to sequence the activities. Any unusual activity sequences within the network
should be fully described within the narrative.

©2013 Project Management Institute. A Guide to the Project Management Body of Knowledge (PMBOK Guide) – Fifth Edition 159
®

Licensed To: Jorge Diego Fuentes Sanchez PMI MemberID: 2399412
This copy is a PMI Member benefit, not for distribution, sale, or reproduction.