Define Activities

Sensei Short Scroll 9 Planning Process Group

Introduction: Why This Matters

The Work Breakdown Structure (WBS) defines what must be delivered. The Define Activities process translates those deliverables into specific actions, the steps that will produce the outputs. This is the foundation of all scheduling work. Without well defined activities, project managers cannot estimate durations, sequence tasks, or create a schedule baseline.

On the PMP exam, questions often test whether you recognize that activities are derived from work packages in the WBS. In practice, clear activity definition supports accurate estimates, realistic schedules, and improved accountability (Project Management Institute, 2021).

Purpose and Objectives

Primary Purpose: To identify and document the specific actions required to produce the project deliverables.

Key Objectives:

Break down work packages into activities that can be scheduled.
Clarify exactly what work is required for each deliverable.
Ensure all team members understand what must be done and by whom.
Prepare inputs for sequencing, estimating, and scheduling.
Produce an activity list, activity attributes, and a milestone list.

Overview

Define Activities is where scope becomes action. The process uses the WBS and schedule management rules to create a complete set of activities that will later be sequenced, estimated, and placed on the schedule.

Bridge from scope to time: Converts work packages into actionable tasks.
Foundation for scheduling: Outputs (activity list, attributes, milestones) feed directly into sequencing and estimation.

Characteristics

Decomposition driven: Breaks work packages into manageable activities.
Progressive elaboration friendly: Supports rolling wave planning when details are limited.
Execution ready: Produces activities that can be estimated, assigned, tracked, and sequenced.
Milestone aware: Captures key checkpoints with zero duration.

Practical Example

Context: A team must deliver a full marketing campaign for a new product (a scope deliverable in the WBS).

Activities:

Develop creative concept: Align messaging, visuals, and channels with goals.
Design multi channel ads: Create digital, print, and video assets.
Secure placements: Lock in publishers, platforms, and timelines.
Launch social campaign: Publish and coordinate content rollout.
Run pre launch testing: Gather feedback and refine assets.
Kick off live campaign: Execute go live across channels.
Evaluate performance: Review metrics and document lessons learned.

Outcome: The deliverable is translated into specific, schedulable work, enabling sequencing and estimating.

Common Pitfalls

Confusing deliverables with activities

Pitfall: Activities are defined at too high a level, simply restating deliverables.
Prevention: Ensure activities represent clear actions, not just outcomes.

Over decomposition

Pitfall: Activities are broken into minute details that encourage micromanagement.
Prevention: Stop decomposition when activities are small enough to estimate and manage effectively.

Ignoring milestones

Pitfall: No clear checkpoints for tracking progress.
Prevention: Always identify and document key milestones with zero duration.

Static activity list

Pitfall: Failing to update activities as scope evolves.
Prevention: Use rolling wave planning and update the list as more detail becomes available.

Sensei Tip : The WBS tells you what must exist at the end. Define Activities tells you what you must actually do to get there. Deliverables come first, actions follow.

Exam Alert : When a question asks what the project manager should do before sequencing or estimating, the best answer is often to create or refine the activity list from the WBS work packages.

Exam Lens

Patterns on the PMP Exam:

If asked where activities come from, the answer is work packages in the WBS, not from the charter or requirements alone.
Questions often test the difference between deliverables (scope) and activities (actions that create deliverables).
Expect milestones to be tested as zero duration events.
When details are unclear, choose rolling wave planning over forcing full detail too early.

Sample Question

Question: A project team creates a list of deliverables but struggles to estimate how long the work will take. What should the project manager do next?

Develop the project schedule.
Create the activity list from the WBS.
Sequence the activities.
Estimate the costs of resources.

Correct Answer: B. Activities must be defined before sequencing or estimating can occur.

Quick Recap Table

Element	Why It Matters	Exam Watch Point
Activity list	Defines all actions needed to produce the project deliverables.	Must be created before sequencing and estimating.
Activity attributes	Adds the detail needed for estimating, sequencing, and assigning work.	Know examples such as predecessors, constraints, and resources.
Milestone list	Identifies key checkpoints and zero duration events.	Exam often tests milestones as having zero duration.
Rolling wave planning	Provides flexibility when details are not yet known.	Expect iterative planning when information is incomplete.

Key Takeaways

Define Activities breaks down deliverables in the WBS into schedulable actions.
Key outputs are the activity list, activity attributes, and milestone list.
Milestones provide critical checkpoints and always have zero duration.
Rolling wave planning supports progressive elaboration when full detail is not available.
On the PMP exam, activities come after work packages and before sequencing and estimation.

Next Step

With activities defined, the next process is Sequence Activities, where the project manager determines the logical order of activities and creates the foundation for the project schedule.

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.

Define Activities