Activity Definition and Sequencing: A Comprehensive Guide for PMP Exam Success
Introduction
Activity Definition and Sequencing are foundational processes within project scope and schedule management. They bridge the gap between what needs to be delivered (the Work Breakdown Structure) and how the project timeline will be constructed. Understanding these processes is critical not only for passing the PMP exam but also for successfully managing real-world projects.
Why Activity Definition and Sequencing Matter
Without clearly defined activities and a logical sequence, a project schedule is essentially meaningless. Here's why these processes are so important:
• They translate deliverables into actionable work: The WBS identifies what must be produced; activity definition breaks those deliverables into the specific tasks needed to produce them.
• They establish logical order: Sequencing determines which activities must come first, which can happen simultaneously, and which depend on the completion of others.
• They enable accurate estimating: You cannot estimate duration or cost without first knowing what the activities are and how they relate to each other.
• They support risk identification: Understanding dependencies helps identify where delays could cascade through the project.
• They form the backbone of the schedule: The network diagram that results from sequencing is the primary input to schedule development techniques such as the Critical Path Method (CPM).
What Is Activity Definition?
Activity Definition is the process of identifying and documenting the specific actions (activities) that must be performed to produce the project deliverables. It takes the work packages from the WBS and decomposes them further into schedulable activities.
Key Inputs:
• Work Breakdown Structure (WBS) and WBS Dictionary: These define the work packages that need to be broken down into activities.
• Project Scope Statement: Provides context including deliverables, constraints, and assumptions.
• Enterprise Environmental Factors (EEFs): Organizational culture, existing systems, industry standards.
• Organizational Process Assets (OPAs): Historical information, templates, lessons learned from previous projects.
Key Tools and Techniques:
• Decomposition: The primary technique — breaking work packages into smaller, more manageable activities. Each activity should be small enough to estimate, schedule, monitor, and control.
• Rolling Wave Planning: Near-term work is planned in detail while future work is planned at a higher level. As the project progresses, future activities are elaborated in greater detail.
• Expert Judgment: Leveraging subject matter experts who have done similar work before.
Key Outputs:
• Activity List: A comprehensive list of all schedule activities required on the project, including an activity identifier and a description of work.
• Activity Attributes: Additional details about each activity such as predecessors, successors, leads and lags, resource requirements, constraints, and assumptions.
• Milestone List: Significant points or events in the project (e.g., phase completion, external deliverable due dates). Milestones have zero duration.
What Is Activity Sequencing?
Activity Sequencing is the process of identifying and documenting the logical relationships (dependencies) among schedule activities. The result is a project schedule network diagram.
Key Inputs:
• Activity List
• Activity Attributes
• Milestone List
• Project Scope Statement
• Organizational Process Assets
Key Tools and Techniques:
1. Precedence Diagramming Method (PDM): Also known as Activity-on-Node (AON), this is the most commonly used method in modern project management and the one primarily tested on the PMP exam. Activities are represented as nodes (boxes), and arrows between them represent dependencies.
PDM supports four types of logical relationships:
• Finish-to-Start (FS): The successor activity cannot start until the predecessor activity finishes. This is the most common relationship type. Example: You must finish pouring the foundation before you start building the walls.
• Finish-to-Finish (FF): The successor activity cannot finish until the predecessor activity finishes. Example: Quality inspection cannot finish until the construction itself finishes.
• Start-to-Start (SS): The successor activity cannot start until the predecessor activity starts. Example: Leveling concrete starts shortly after pouring concrete starts.
• Start-to-Finish (SF): The successor activity cannot finish until the predecessor activity starts. This is the rarest relationship and is seldom used in practice. Example: The old security system cannot be decommissioned (finished) until the new security system starts operating.
2. Dependency Determination and Integration:
• Mandatory Dependencies (Hard Logic): Inherent in the nature of the work. They are physically required. Example: You must design before you can build.
• Discretionary Dependencies (Soft Logic / Preferred Logic): Based on best practices, preferences, or team decisions. They can be changed if needed. Example: Choosing to complete all design work before starting any construction, even though some overlap might be possible.
• External Dependencies: Relationships between project activities and non-project activities. Example: Government approval must be obtained before construction can begin.
• Internal Dependencies: Relationships between project activities that are within the project team's control.
3. Leads and Lags:
• Lead: The amount of time a successor activity can be advanced with respect to its predecessor. It accelerates the successor. Example: With a 5-day lead on an FS relationship, the successor starts 5 days before the predecessor finishes (fast-tracking).
• Lag: The amount of time a successor activity is delayed with respect to its predecessor. Example: After pouring concrete, you must wait 3 days for it to cure before building on it — that's a 3-day lag.
Key Outputs:
• Project Schedule Network Diagram: A graphical representation of the logical relationships among the project schedule activities. It shows the flow of work and is used as an input to schedule development.
• Updated Project Documents: Activity lists, activity attributes, and assumption logs may be updated.
How Activity Definition and Sequencing Work Together
Think of these processes as a pipeline:
1. The WBS defines work packages (deliverable-oriented).
2. Activity Definition decomposes work packages into activities (action-oriented).
3. Activity Sequencing arranges those activities in logical order, creating the network diagram.
4. The network diagram feeds into duration estimating and schedule development (including Critical Path Method analysis).
Without step 2, you don't have schedulable units of work. Without step 3, you don't know the order of work or the critical path.
Key Concepts to Remember for the PMP Exam
• Activities are NOT the same as work packages. Work packages are the lowest level of the WBS; activities are derived from work packages and appear in the activity list, not the WBS itself.
• Milestones have zero duration. They represent a point in time, not work effort.
• Finish-to-Start is the default and most common dependency type.
• Mandatory dependencies cannot be changed; discretionary dependencies can be modified during schedule compression (particularly fast-tracking).
• Leads accelerate; lags delay. Leads are essentially negative time on a dependency; lags are positive waiting time.
• Rolling wave planning is an iterative planning technique — it is NOT a sign of poor planning. It is appropriate when future work cannot yet be fully detailed.
• Start-to-Finish (SF) is the rarest dependency type. If you see it on the exam, read very carefully — it is often used as a distractor.
• The network diagram shows logical relationships, NOT the timeline (that's the schedule or Gantt chart).
Exam Tips: Answering Questions on Activity Definition and Sequencing
1. Distinguish between WBS and Activity List: If a question asks about deliverables and scope decomposition, think WBS. If it asks about schedule activities and tasks, think Activity List. The exam will try to blur this line — stay sharp.
2. Know your dependency types cold: Be able to identify FS, FF, SS, and SF from scenario descriptions. The exam loves to describe a real-world situation and ask you to name the dependency type. Practice by creating examples of each type.
3. Lead vs. Lag — don't confuse them: A common trap is reversing leads and lags. Remember: Lead = overlap (acceleration), Lag = wait (delay). If the question says "the next activity can start 2 days before the current one finishes," that's a 2-day lead on an FS relationship.
4. Mandatory vs. Discretionary Dependencies: When a question involves schedule compression (especially fast-tracking), the correct approach involves adjusting discretionary dependencies, not mandatory ones. If someone suggests changing a mandatory dependency, that answer is almost always wrong.
5. Read scenario questions carefully: Many questions will present a situation where the PM is trying to build a schedule. The correct first step is usually to define activities, then sequence them, then estimate durations, then develop the schedule. If a question asks what to do first and the WBS is already complete, the answer is likely "Define Activities."
6. Network diagram questions: You may be asked to draw or interpret a simple network diagram. Practice identifying the critical path, understanding parallel paths, and applying leads and lags. Know that the network diagram is the output of sequencing, not estimating.
7. Watch for the word "milestone": If an answer choice includes assigning duration to a milestone, it's wrong. Milestones always have zero duration.
8. Rolling Wave Planning is legitimate: If a question describes a situation where the team cannot define all activities at the project start, and an answer choice involves planning near-term work in detail while leaving future work at a high level, that answer (rolling wave planning) is likely correct. Do NOT choose an answer that says "wait until all details are known" — that would be unrealistic in most project scenarios.
9. External dependencies are risks: If a question involves an activity that depends on a third party or external event, recognize it as an external dependency and connect it to risk management. External dependencies are often beyond the project manager's control.
10. Process order matters: The PMP exam may test whether you understand the logical flow of planning processes. Activity Definition comes before Activity Sequencing, which comes before Duration Estimating, which comes before Schedule Development. If a question asks what comes next after the WBS is approved, Activity Definition is typically the correct answer.
11. Agile/Hybrid Considerations (PMBOK 7th/8th Edition): In agile or hybrid environments, activity definition and sequencing may happen iteratively within each sprint or iteration. The backlog items are refined and ordered based on priority and dependencies. If the exam presents an agile scenario, focus on iterative elaboration, backlog refinement, and just-in-time planning rather than comprehensive upfront sequencing.
12. Elimination Strategy: When in doubt, eliminate answers that confuse outputs of one process with another. For example, an answer that lists "project schedule" as an output of Activity Sequencing is incorrect — the schedule is an output of Schedule Development. The output of sequencing is the network diagram.
Summary
Activity Definition and Sequencing are essential building blocks of project schedule management. Activity Definition transforms deliverables into actionable tasks, while Activity Sequencing establishes the logical order and dependencies among those tasks. Together, they produce the network diagram that drives critical path analysis and schedule development. Mastering the dependency types (FS, FF, SS, SF), understanding leads and lags, and knowing the difference between mandatory and discretionary dependencies will give you a significant advantage on the PMP exam. Practice with real-world scenarios, memorize the process inputs and outputs, and always read exam questions carefully to distinguish between closely related concepts.
