Glossary of Technical Terms Used in Pipeline Construction: Start to Start Lag

Start to Start Lag

Understanding Start-to-Start Lag in Project Planning & Scheduling

In the realm of project planning and scheduling, ensuring smooth workflow and optimizing resource allocation is crucial. One key concept that contributes to this is Start-to-Start Lag (SS Lag). This article aims to demystify this term and demonstrate its significance in achieving project success.

Definition:

Start-to-Start Lag, or SS Lag, defines the minimum amount of time that must pass between the commencement of one activity and the start of its successor(s). This delay can be expressed either as a specific duration (e.g., 3 days) or as a percentage of the predecessor activity's duration (e.g., 20%).

Why is SS Lag Important?

SS Lag plays a vital role in project planning and scheduling for several reasons:

  • Resource Availability: Implementing an SS Lag ensures that the resources required for the subsequent activity become available only after the predecessor activity has been underway for a specific duration. This prevents resource conflicts and facilitates a smooth transition between activities.
  • Dependency Management: SS Lag establishes a clear dependency relationship between activities. The start of the successor activity is contingent upon the progress of the predecessor, preventing premature initiation of tasks that rely on deliverables from previous activities.
  • Avoiding Bottlenecks: By strategically incorporating SS Lag, project managers can anticipate potential bottlenecks and plan accordingly. This ensures that the project timeline is maintained and that critical tasks are not delayed due to insufficient lead time.
  • Improved Project Quality: SS Lag helps maintain project quality by allowing ample time for tasks to be completed thoroughly and for potential issues to be addressed before moving on to the next phase.

Examples of SS Lag in Action:

  1. Software Development: Before starting the testing phase of a software project, a minimum of two weeks must pass after the development phase commences. This allows for sufficient code review and documentation to be completed, ensuring a robust and well-documented product for testing.
  2. Construction Project: The start of the painting phase cannot begin until the drywall installation phase has progressed for at least 3 days, allowing for adequate drying time and ensuring the painting process is not hindered by damp surfaces.

Key Points to Remember:

  • SS Lag can be applied to multiple successor activities, creating complex dependency chains.
  • The specific SS Lag value should be determined based on the nature of the activities and the project's overall requirements.
  • Utilizing project management software can significantly simplify the implementation and tracking of SS Lag within a project schedule.

Conclusion:

Understanding and effectively utilizing Start-to-Start Lag is essential for successful project planning and scheduling. By strategically implementing SS Lag, project managers can streamline workflow, optimize resource allocation, and ensure the timely delivery of high-quality deliverables. This critical concept empowers project teams to navigate complex dependencies, anticipate bottlenecks, and achieve project goals with greater efficiency.


Test Your Knowledge

Quiz on Start-to-Start Lag

Instructions: Choose the best answer for each question.

1. What does Start-to-Start Lag (SS Lag) define?

a) The minimum time between the completion of one activity and the start of its successor. b) The minimum time between the start of one activity and the start of its successor. c) The maximum time between the start of one activity and the start of its successor. d) The maximum time between the completion of one activity and the start of its successor.

Answer

b) The minimum time between the start of one activity and the start of its successor.

2. Which of these is NOT a benefit of using SS Lag in project planning?

a) Improved resource allocation. b) Reduced project risk. c) Increased project complexity. d) Enhanced dependency management.

Answer

c) Increased project complexity.

3. In a software development project, why might a 2-week SS Lag be implemented between the development phase and the testing phase?

a) To allow time for code review and documentation. b) To allow the testing team to familiarize themselves with the project. c) To ensure the development team is ready to address any bugs found during testing. d) To give the project manager time to assess project progress.

Answer

a) To allow time for code review and documentation.

4. What is a key consideration when determining the appropriate SS Lag value for an activity?

a) The budget of the project. b) The availability of project stakeholders. c) The nature of the activity and its dependencies. d) The number of resources available.

Answer

c) The nature of the activity and its dependencies.

5. Which of these tools can be helpful for managing and tracking SS Lag within a project schedule?

a) Spreadsheets. b) Project management software. c) Communication tools. d) All of the above.

Answer

d) All of the above.

Exercise:

Scenario: You are planning a website redesign project. The following activities are involved:

  1. Design Concept Development (DC)
  2. Content Creation (CC)
  3. Development (DEV)
  4. Testing (TEST)
  5. Deployment (DEP)

Dependencies:

  • CC depends on DC.
  • DEV depends on both DC and CC.
  • TEST depends on DEV.
  • DEP depends on TEST.

Requirements:

  • A minimum of 2 days must pass between the start of DC and the start of CC.
  • A minimum of 3 days must pass between the start of DEV and the start of TEST.

Task:

  1. Identify the SS Lags that need to be implemented based on the given dependencies and requirements.
  2. Draw a simple network diagram to illustrate the project schedule with the identified SS Lags.

Exercice Correction

SS Lags:

  • **DC to CC:** 2 days
  • **DEV to TEST:** 3 days

Network Diagram:

A simple network diagram could use boxes to represent each activity and arrows to represent dependencies. The SS Lags would be indicated on the arrows, for example:

DC -->[2 days] CC --> DEV -->[3 days] TEST --> DEP


Books

  • Project Management Institute (PMI). (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (7th ed.). Project Management Institute. (Chapter 6: Schedule Management) - Provides a comprehensive overview of scheduling techniques, including lag and lead.
  • Kerzner, H. (2017). Project Management: A Systems Approach to Planning, Scheduling, and Controlling (12th ed.). Wiley. (Chapter 9: Network Planning and Scheduling) - Covers network diagrams, critical path method, and different types of dependencies, including SS Lag.
  • Meredith, J. R., & Mantel, S. J. (2017). Project Management: A Managerial Approach (11th ed.). John Wiley & Sons. (Chapter 9: Network Planning and Scheduling) - Offers a practical approach to scheduling and project management, including discussions on dependencies and lag.

Articles

  • "Start-to-Start Lag: Definition, Importance, and Examples" by [Your Name]: This article you've drafted is a great starting point! It provides a clear explanation of SS Lag, its importance, and examples.
  • "Lag vs. Lead in Project Management" by ProjectManager.com: This article differentiates between lag and lead, providing practical examples and tips for their application.
  • "Understanding and Using Lag in Project Scheduling" by Smartsheet: This resource explores different types of lag, their impact on scheduling, and how to use them effectively.

Online Resources

  • ProjectManager.com: This website offers a wealth of information on project management topics, including a dedicated section on scheduling and dependencies.
  • Smartsheet: Provides free resources and tutorials on project scheduling, including explanations of lag, lead, and their application in project management software.
  • PMI.org: The Project Management Institute's website offers a variety of resources, including articles, webinars, and training materials on various project management topics, including schedule management.

Search Tips

  • Use specific keywords: "Start-to-Start Lag," "Project Scheduling Lag," "Lag in Project Management," "SS Lag," "Dependency Relationship in Project Management."
  • Combine keywords with project management software names: "Start-to-Start Lag in Microsoft Project," "SS Lag in Smartsheet," "Lag in Asana."
  • Search for specific scenarios: "Example of Start-to-Start Lag in Construction," "Using SS Lag in Software Development."
Similar Terms
Drilling & Well Completion
Safety Training & Awareness
Communication & Reporting
Project Planning & Scheduling
Instrumentation & Control Engineering
Risk Management
Oil & Gas Specific Terms
Oil & Gas Processing
IT Infrastructure
Lifting & Rigging
Most Viewed

Comments


No Comments
POST COMMENT
captcha
Back