Sequence Activities

Sensei Short Scroll 10 Planning Process Group

Sequence Activities

Introduction: Why This Matters

Once activities are defined, they must be arranged in the order they will be performed. The Sequence Activities process determines logical relationships among activities, identifies dependencies, and creates the foundation for a realistic project schedule (Project Management Institute, 2021).

Without proper sequencing, a project manager cannot identify the critical path, assess float, or anticipate bottlenecks. On the PMP exam, many situational questions require you to know the correct type of dependency and to recognize that activities must be sequenced before scheduling and duration estimates.

Purpose and Objectives

Primary Purpose: To identify and document logical relationships among project activities.

Key Objectives:

  • Determine the correct order of work.
  • Identify mandatory and discretionary dependencies.
  • Document leads and lags between activities.
  • Create the project schedule network diagram.
  • Provide the basis for developing the project schedule and critical path analysis.

Overview

Sequence Activities connects tasks into a logical flow. Using the activity list and attributes, the team identifies relationships, confirms dependency types, and builds a network diagram that supports schedule development and critical path analysis.

  • Turns a list into a flow: Activities become a connected network.
  • Makes constraints visible: Dependencies, leads, and lags reveal where work can or cannot overlap.
  • Sets up critical path analysis: A correct network diagram is assumed for float and critical path questions.

Characteristics

  • Relationship based: Connects activities using dependency logic.
  • PDM centered: Uses Precedence Diagramming Method for network diagrams.
  • Dependency aware: Distinguishes mandatory, discretionary, external, and internal dependencies.
  • Timing adjustable: Uses leads and lags to model overlap or delays.

Practical Example

Context: A construction project is building a two story office building.

Activities:

  • Excavation → Foundation (FS): Foundation cannot start until excavation is complete.
  • Foundation → Framing (FS with five day lag): Allow five days for curing after foundation before framing begins.
  • Framing → Electrical rough in (SS with three day lag): Electrical work can begin once framing has started and progressed three days.
  • Painting → Inspections (FF): Inspections cannot finish until painting finishes.

Outcome: The team produces a network diagram that shows the critical path and dependencies, enabling accurate schedule development and risk analysis.

Common Pitfalls

Overlooking external dependencies

  • Pitfall: Ignoring vendor deliveries, regulatory approvals, or third party actions.
  • Prevention: Engage stakeholders and document external dependencies early.

Misusing discretionary dependencies

  • Pitfall: Sequencing based on personal preference rather than documented logic.
  • Prevention: Document discretionary choices and revisit them during schedule optimization.

Confusing leads and lags

  • Pitfall: Misclassifying overlaps and delays.
  • Prevention: Remember that leads accelerate successors, lags delay successors.

Unclear documentation

  • Pitfall: Teams cannot agree on sequencing because relationships are vague.
  • Prevention: Use network diagrams and activity attributes to clearly record relationships.

Sensei Tip : The WBS tells you what must be delivered, Define Activities tells you what must be done, and Sequence Activities tells you in what order the work should flow. Master that sequence in your mind and many exam questions become much easier.

Exam Alert : If a question asks for the correct step before developing the schedule, the answer is often to sequence activities. A connected network diagram must exist before critical path and float analysis can be valid.

Exam Lens

Patterns on the PMP Exam:

  • If asked about the correct first step in creating the schedule, the answer is usually sequence activities before estimating durations.
  • Scenarios may describe a curing period in construction (a lag) or overlapping work such as early testing (a lead).
  • Expect to identify dependency types: mandatory vs discretionary, internal vs external.
  • Many critical path and float questions assume a correctly built network diagram from Sequence Activities.

Sample Question

Question: The project team needs to start system testing two days before coding is finished. How should this relationship be documented?

  1. Finish to Start with a two day lag
  2. Finish to Start with a two day lead
  3. Start to Start with a two day lag
  4. Finish to Finish with a two day lead

Correct Answer: B. This is a Finish to Start relationship with a lead, since the successor begins earlier than the predecessor finishes.

Quick Recap Table

Element Why It Matters Exam Watch Point
Precedence diagramming Creates a network diagram of linked activities. Know FS, FF, SS, and SF relationships.
Dependency types Clarify logical order and constraints on work. Identify mandatory vs discretionary, internal vs external.
Leads and lags Adjust the timing of relationships between activities. Leads create overlap, lags add delay.
Network diagram Provides the foundation for the schedule baseline and critical path. Often used in critical path and float questions.

Key Takeaways

  • Sequence Activities establishes the logical order of project work.
  • Dependencies can be mandatory, discretionary, external, or internal.
  • Leads accelerate successor activities, while lags delay them.
  • The primary output is the project schedule network diagram.
  • On the PMP exam, sequencing is performed before estimating durations or developing the detailed schedule baseline.

Next Step

With activities sequenced, the next process is Estimate Activity Durations, where the project manager and team determine how long each activity will take, moving toward the schedule baseline.

Bibliography

Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (Project Management Body of Knowledge Guide) (7th ed.). Project Management Institute.

Scroll to Top