Activity Attributes
A set of descriptive details captured for every scheduled activity in the activity list. These details may include items like activity identifiers or codes; predecessors and successors; the type of dependency between activities; any leads or lags; resource needs; target or imposed dates; constraints; and key assumptions.
Key Points
- They are metadata about an activity that help define, organize, and control the schedule.
- Typical items include activity codes, predecessors, successors, relationship types, leads/lags, resource requirements, imposed dates, constraints, and assumptions.
- They support sequencing, estimating durations and costs, resource planning, and schedule analysis (e.g., critical path and network logic).
- Attributes can be refined over time as more information becomes available, enabling better filtering, grouping, and reporting.
Example
For activity A-104 “Install Server OS”: activity code A-104; predecessor A-103 “Rack Servers” with a finish-to-start relationship and a 2‑day lag; successor A-105 “Configure Network”; resources: 1 systems engineer and 1 technician; imposed date: start no earlier than May 10; constraint: hardware must pass burn-in; assumption: network VLANs will be available by May 9.
PMP Example Question
Which project document records details such as an activity’s predecessors and successors, dependency type, leads and lags, resource needs, imposed dates, constraints, and assumptions?
- Activity List
- Activity Attributes
- WBS Dictionary
- Milestone List
Correct Answer: B — Activity Attributes
Explanation: Activity attributes capture descriptive data for each activity, including codes, logical relationships, leads/lags, resource requirements, imposed dates, constraints, and assumptions.
